<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 4, 2016 at 4:13 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Feb 04, 2016 at 03:34:05PM +0530, Raghavendra Talur wrote:<br>
> Hi,<br>
><br>
> We recently changed the jenkins builds to be triggered on the following<br>
> triggers.<br>
><br>
> 1. Verified+1<br>
> 2. Code-review+2<br>
> 3. recheck (netbsd|centos|smoke)<br>
><br>
> There is a bug in 1 and 2.<br>
><br>
> Multiple triggers of 1 or 2 would result in re-runs even when not intended.<br>
><br>
> I would like to replace 1 and 2 with a comment "run-all-regression" or<br>
> something like that.<br>
> Thoughts?<br>
<br>
</span>Maybe starting regressions on Code-Review +1 (or +2) only?<br></blockquote><div><br></div><div>Multiple code-reviews would do multiple triggers. Won't work.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
Niels<br>
</font></span></blockquote></div><br></div></div>