<div dir="ltr"><div><div>yep, using on Jenkins the plugin Gerrit Trigger, this plugin trigger all requests for all repositories and all branches, this function running with Auto QA tests and vote with ACL "verified", for example:</div><div><br></div><div> <a href="https://gerrit.ovirt.org/#/c/37886/">https://gerrit.ovirt.org/#/c/37886/</a></div></div><div><br></div><div>my intention is make one deploy with one complete example the use this, comming soon :D</div><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><br>firemanxbr</div></div></div>
<br><div class="gmail_quote">On Wed, Apr 1, 2015 at 4:32 AM, Emmanuel Dreyfus <span dir="ltr"><<a href="mailto:manu@netbsd.org" target="_blank">manu@netbsd.org</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 Wed, Apr 01, 2015 at 12:50:30PM +0530, Vijay Bellur wrote:<br>
> I think all we need is to create another gerrit user like "NetBSD<br>
> Regression" or so and have verified votes routed through this user. Just as<br>
> multiple users can provide distinct CR votes, we can have multiple build<br>
> systems provide distinct Verified votes.<br>
<br>
</span>Yes, plase do that: a nb7build user like we have a build user. It can have<br>
the same .ssh/authorized_keys as build user.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Emmanuel Dreyfus<br>
<a href="mailto:manu@netbsd.org">manu@netbsd.org</a><br>
</font></span></blockquote></div><br></div></div>