<div dir="ltr"><div class="gmail_extra">On Mon, May 12, 2014 at 4:23 PM, Justin Clift <span dir="ltr"><<a href="mailto:justin@gluster.org" target="_blank">justin@gluster.org</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 12/05/2014, at 9:04 PM, Anand Avati wrote:<br>
<snip><br>
<div class="">> And yeah, the other reason: if a dev pushes a series/set of dependent patches, regression needs to run only on the last one (regression test/voting is cumulative for the set). Running regression on all the individual patches (like a smoke test) would be very wasteful, and tricky to avoid (this was the part which I couldn't solve)<br>
<br>
</div>What's the manual "with intelligence required" process we use to<br>
do this atm? eg for people wanting to test the combined patch<br>
set<br>
<br>
Side note - I'm mucking around with the Gerrit Trigger plugin in<br>
a VM on my desktop running Jenkins. So if you see any strangeness<br>
in things with Gerrit comments, it could be me. (feel free to ping<br>
me as needed)<br><br></blockquote><div><br></div><div><a href="http://build.gluster.org/job/regression/build">http://build.gluster.org/job/regression/build</a> - key in the gerrit patch number for the CHANGE_ID field, and click 'Build'.<br>
</div><div><br></div><div><br></div></div></div></div>