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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Thu, Feb 4, 2016 at 4:13 PM, Niels de Vos <ndevos@xxxxxxxxxx> 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.
 

Niels

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux