Difference between revisions of "Continuous Integration"
From iDempiere en
CarlosRuiz (talk | contribs) (documenting continous integration) |
CarlosRuiz (talk | contribs) |
||
| Line 9: | Line 9: | ||
* iDempiere job checks for changes on development branch at repository every 5 minutes and compiles the p2 repository | * iDempiere job checks for changes on development branch at repository every 5 minutes and compiles the p2 repository | ||
** it also creates a linux installer 64 bit installer, but is mostly for checking that compilation is not broken | ** it also creates a linux installer 64 bit installer, but is mostly for checking that compilation is not broken | ||
| + | ** this job does not create a seed database, so using this one requires applying migration scripts | ||
* iDempiere2.1 job does the same but on release-2.1 branch | * iDempiere2.1 job does the same but on release-2.1 branch | ||
Revision as of 20:13, 21 July 2015
iDempiere manages continuous integration using Jenkins
Website
The website is located at http://ci.idempiere.org - it can can be referred also with the alias http://jenkins.idempiere.com
Jobs
- iDempiere job checks for changes on development branch at repository every 5 minutes and compiles the p2 repository
- it also creates a linux installer 64 bit installer, but is mostly for checking that compilation is not broken
- this job does not create a seed database, so using this one requires applying migration scripts
- iDempiere2.1 job does the same but on release-2.1 branch
- iDempiereDaily and iDempiere2.1Daily does a different job at 9PM and 11PM (GMT-5) respectively
- it checks for changes at repository
- create seed databases for postgresql>=9.1 and oracle>=10g
- create installers for Linux, Windows, Mac, Solaris 32 and 64 bits, and also a .deb Ubuntu installer
Notifications
Issues on compilation are caught by the continuous integration jobs and notified to google dev group. Issues on scripts are caught by the daily installer and notified samely.
