Jenkins Continuous Integration Server for oVirt is up and running!

[Jon Choate]

Can you clarify what will trigger a build? Is it a push to Gerrit to 
initiate a review or is it after the code has been reviewed and it is 
merged into the repository? Or maybe both?


On 01/19/2012 05:07 AM, Eyal Edri wrote:
> fyi,
>
> oVirt project now has a Jenkins CI server[1] on http://jenkins.ovirt.org.
>
> The CI server runs various jobs on oVirt components *[2] such as ovirt-engine,ovirt-node,etc..
> Every commit to gerrit.ovirt.org will trigger the job 'ovirt_engine' which will run 'maven' build and verify that the commit didn't break the code.
> If the commit did break the code, it will send an alert email to "engine-patches.ovirt.org" and to the commiter with a link to a log console containing the error.
> On success, the job will trigger other jobs such as "find_bugs", "gwt profiles", "create db", "unit-tests", each testing a different part of the code.
>
> In time, more and more jobs will be added to jenkins, which will allow us to catch bugs much faster than before, and to improve code quality even more.
> If you have questions, don't hesitate to ask me or infra at ovirt.org.
>
> [1] http://jenkins-ci.org/
> [2] currently only ovirt-engine is configured and working.
>
>
> Eyal Edri
> oVirt infrastructure team
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra