I saw a presentation at the JUC 2013 @Palo Alto of its usage in the OpenStack project: seems really interesting !
Luca. On 28 Jan 2014, at 08:46, Robert Ward <[email protected]> wrote: > Regarding 2, a piece of software I came across awhile ago called zuul[1] > sounds like it might do what you want. I haven't got around to looking at it > in detail yet so don't know how it works but it might be what you need. I > believe the source is on openstacks github account. > > I would be interested to know how it goes if you give it a try or if anyone > is already using it how it performs in your workflow. > > Cheers, > > Rob > > [1] - http://ci.openstack.org/zuul/ > > On 28 Jan 2014 08:34, "Luca Milanesio" <[email protected]> wrote: > > > > Hi JianHua, > > looping the Gerrit mailing list as people may have answers from there as > > well. > > > > From knowledge of the plugin, the answers are: > > > > 1. Yes: just add the extra event to be monitored in the plugin. > > > > 2. No: you can trigger another build *after* the patch is merged but not > > before (unless you accept as valid the last validation of the last > > patch-set) > > > > Luca. > > > > > > > > On 28 Jan 2014, at 03:15, JianHua Geng <[email protected]> wrote: > > > >> Hi All, > >> > >> I am working on Jenkins and Gerrit integration recently, and I am using > >> the gerrit-trigger plugin. > >> > >> Now I can trigger my jenkins job when patch has been created in my gerrit. > >> My questions are: > >> 1. How can I retrigger my job when I publish some special comments on the > >> patch in gerrit? > >> For example, I publish a comment "recheck" and retrigger the jenkins job > >> to verify my patch again automatically? > >> > >> 2. Is it possible to let the jenkins job verify my patch before it is > >> merged? > >> Now, the gerrit-trigger plugin can trigger the job after the change is > >> merged, but my purpose is let the jenkins job verify it before merged to > >> make it more safe, once the job fail the merge request should be rejected. > >> > >> Thanks in advance. > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Jenkins Users" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to [email protected]. > >> For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > > -- > > To unsubscribe, email [email protected] > > More info at http://groups.google.com/group/repo-discuss?hl=en > > > > --- > > You received this message because you are subscribed to the Google Groups > > "Repo and Gerrit Discussion" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
