[Gluster-devel] [Gluster-infra] Code-Review+2 and Verified+1 cause multiple retriggers on Jenkins

[Niels de Vos]

On Thu, Feb 04, 2016 at 04:15:16PM +0530, Raghavendra Talur wrote:
> On Thu, Feb 4, 2016 at 4:13 PM, Niels de Vos <ndevos at redhat.com> wrote:
> 
> > 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?
> >
> 
> Multiple code-reviews would do multiple triggers. Won't work.

How can we make this to work, without the need of providing magic
comments?

Niels
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20160204/8f812449/attachment-0001.sig>