Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [capella-dev] Builds on Github

Hi,

 

An update about tests / contribution / review process :

 

Job has been migrated to:

https://ci.eclipse.org/capella/job/capella-product/

 

cid:image003.png@01D5CC91.2AB77CD0

 

For each pull request, a job is created automatically :  (or click on to detect new pull requests : https://ci.eclipse.org/capella/job/capella-product/build?delay=0)

https://ci.eclipse.org/capella/job/capella-product/view/change-requests/

 

cid:image006.png@01D5CC91.2AB77CD0

 

 

 

 

For commiters: (classical github process)

 

-          Clone eclipse/capella repository, do your stuff, then push a new branch with a pull request for it.

 

 

For non commiters: (classical github process)

 

-          You have to fork https://github.com/eclipse/capella repository then create a pull request towards the eclipse/capella target branch.

cid:image002.png@01D5CC92.AC4A2710

 

-          Clone your repository, do your stuff, then push a new branch.

 

-          On your branch, create a pull request towards the capella repository.

 

-          cid:image004.png@01D5CC92.AC4A2710

 

cid:image001.png@01D5CC93.2BFF5430

-          For already-known non-commiters, a build will be trigger automatically.

(Pull requests are tested automatically for known-non-commiters, otherwise, ask a commiter to trigger tests on your pull request (https://ci.eclipse.org/capella/job/capella-product-pull-request-manual/) )

 

 

Regards,

Philippe

 

From: DUL Philippe
Sent: mercredi 15 janvier 2020 13:20
To: 'capella-dev@xxxxxxxxxxx'
Subject: Builds on Github

 

Hi everyone,

 

Starting today, git.polarsys.org may become unavailable on short notice.

So it is time to switch on github, even to run our junit tests.

 

 

Like any other projects on Github, bitbucket, or gitlab, contributions are done with Pull Requests:

 

Right now, just push a new branch (<issue-id for instance>) and create a pull request on the targeted branch.

-          For commiters, you don’t have to fork the repository,

-          For non commiters, you have to fork it.

 

 

Tests can be triggered manually on a given pull request:

 

https://ci.eclipse.org/capella/job/capella-product-gh/

 

cid:image007.png@01D5CC91.2AB77CD0

Put in PULL_REQUEST the id of the pull request.

 

(for instance, if the pull request is https://github.com/eclipse/capella/pull/1, put 1)

This will trigger capella-product on the given pull request head commit.

Then, will trigger capella-product-test as done in gerrit.

(of instance: https://ci.eclipse.org/capella/job/capella-product-tests/271/ for this pull request 1)

 

 

 

We still don’t have a way to automatically trigger tests on github.

But:

In a near future, we tend  to have automatically junit tests, like codewind did:

https://ci.eclipse.org/codewind/job/Codewind/job/codewind/

 

cid:image008.png@01D5CC91.2AB77CD0

 

 

cid:image009.png@01D5CC91.2AB77CD0

 

 

https://github.com/eclipse/codewind/pull/1755

cid:image010.png@01D5CC91.2AB77CD0

 

 

Best regards

Philippe

 


Back to the top