<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 12, 2014 at 4:39 PM, Justin Clift <span dir="ltr"><<a href="mailto:justin@gluster.org" target="_blank">justin@gluster.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 13/05/2014, at 12:27 AM, Anand Avati wrote:<br>
<snip><br>
<div class="">> <a href="http://build.gluster.org/job/regression/build" target="_blank">http://build.gluster.org/job/regression/build</a> - key in the gerrit patch number for the CHANGE_ID field, and click 'Build'.<br>
<br>
</div>Doesn't that just apply the given change to HEAD of its<br>
associated branch? eg it won't apply dependent commits<br>
first?</blockquote><div><br></div><div style>No, this is just for jenkins to run tests and vote on gerrit. Applying a change into HEAD is done by sub/maintainers having commit rights to the project in Gerrit. However Gerrit prevents even a maintainer from committing until there is +2 code review vote and +1 verified vote (no matter who votes - Jenkins or someone else)</div>
<div style><br></div><div style> </div></div></div></div>