Re: [Gluster-infra] Code-Review+2 and Verified+1 cause multiple retriggers on Jenkins
On Thu, Feb 04, 2016 at 03:34:05PM +0530, Raghavendra Talur wrote: > Hi, > > We recently changed the jenkins builds to be triggered on the following > triggers. > > 1. Verified+1 > 2. Code-review+2 > 3. recheck (netbsd|centos|smoke) > > There is a bug in 1 and 2. > > Multiple triggers of 1 or 2 would result in re-runs even when not intended. > > I would like to replace 1 and 2 with a comment "run-all-regression" or > something like that. > Thoughts? Maybe starting regressions on Code-Review +1 (or +2) only? Niels signature.asc Description: PGP signature ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] [Gluster-devel] Code-Review+2 and Verified+1 cause multiple retriggers on Jenkins
On 02/04/2016 03:39 PM, Kaushal M wrote: I'm okay with this. +1 On Thu, Feb 4, 2016 at 3:34 PM, Raghavendra Talurwrote: Hi, We recently changed the jenkins builds to be triggered on the following triggers. 1. Verified+1 2. Code-review+2 3. recheck (netbsd|centos|smoke) There is a bug in 1 and 2. Multiple triggers of 1 or 2 would result in re-runs even when not intended. I would like to replace 1 and 2 with a comment "run-all-regression" or something like that. Thoughts? Thanks Raghavendra Talur ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra ___ Gluster-devel mailing list gluster-de...@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra