[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[mdmbl-dev] Jenkins build (CI) set up
|
Hi there,
we're now having the initial CI set up, i.e. our JIPP (Jenkins Instance Per Project) is running (https://ci.eclipse.org/mdmbl). Currently 3 pipeline builds are configured:
1) openMDM_Application_nightly
* Builds the org.eclipse.mdm.nucleus based on a composite build, i.e. including api.base, api.default and api.odsadapter every day around midnight
* Based on dev branch
* Build artifacts can be downloaded at the moment via http://download.eclipse.org/mdmbl/nightly/application/?d
2) openMDM_Application_Gerrit
* Based on the nightly openMDM application build
* Triggered by any push to Gerrit to one of the following repositories
* org.eclipse.mdm.api.base
* org.eclipse.mdm.api.default
* org.eclipse.mdm.api.odsadapter
*org.eclipse.mdm.nucleus
* Sends "Verified +1" / "Verified -1" in case of success / failure to Gerrit
* Limitation: only Gerrit patchset of 1 project repository can be handled, i.e. the change must be buildable using the current HEAD of the dev branch of all other repositories than the one with the Gerrit change pushed. In the case of simultaneously we have to manually test buildability.
3) openMDM_org.eclipse.mdm.realms_nightly
* Builds the org.eclipse.mdm.realms every day around midnight
* Based on dev branch
* Build artifacts can be downloaded at the moment via http://download.eclipse.org/mdmbl/nightly/org.eclipse.mdm.realms/?d
Best regards
Alex
-----------------------------------------------------------------
Alexander Nehmer
Senior Software Engineer
science + computing ag
Phone: +49 (0) 7071 9457-633
Mobile: +49 (0) 171 550 86 94
E-Mail: alexander.nehmer@xxxxxxxx
Hagellocher Weg 73
D-72070 Tuebingen
Website: de.atos.net/sc