On Mon, May 12, 2014 at 4:23 PM, Justin Clift <justin@xxxxxxxxxxx> wrote:
On 12/05/2014, at 9:04 PM, Anand Avati wrote:
<snip>
> 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)What's the manual "with intelligence required" process we use to
do this atm? eg for people wanting to test the combined patch
set
Side note - I'm mucking around with the Gerrit Trigger plugin in
a VM on my desktop running Jenkins. So if you see any strangeness
in things with Gerrit comments, it could be me. (feel free to ping
me as needed)
http://build.gluster.org/job/regression/build - key in the gerrit patch number for the CHANGE_ID field, and click 'Build'.
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
