<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 14, 2016 at 10:32 AM, Ravishankar N <span dir="ltr"><<a href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01/08/2016 12:03 PM, Raghavendra Talur wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
P.S: Stop using the "universal" jenkins account to trigger jenkins build if you are not a maintainer.<br>
If you are a maintainer and don't have your own jenkins account then get one soon!<br>
<br>
</blockquote>
<br>
I would request for a jenkins account for non-maintainers too, at least for the devs who are actively contributing code (as opposed to random one-off commits from persons). That way, if the regression failure is *definitely* not in my patch (or) is a spurious failure (or) is something that I need to take a netbsd slave offline to debug etc., I don't have to be blocked on the Maintainer. Since the accounts are anyway tied to an individual, it should be easy to spot if someone habitually re-trigger regressions without any initial debugging.<br>
<br></blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-Ravi<br>
</blockquote></div><br></div></div>