<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">I agree, and only vote +1 myself, but I don’t agree on mandating it. If someone has invested enough in their CI to be confident, we just supply rope.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">doug</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Jun 25, 2015, at 8:08 AM, John Davidge (jodavidg) <<a href="mailto:jodavidg@cisco.com" class="">jodavidg@cisco.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Hi all,</div>
<div class=""><br class="">
</div>
<div class="">Recent neutron third party CI issues have got me thinking again about a topic which we discussed in Vancouver:</div>
<div class=""><br class="">
</div>
<div class="">Should any Third Party CI have voting rights for neutron patches in gerrit?</div>
<div class=""><br class="">
</div>
<div class="">I’d like to suggest that they shouldn’t.</div>
<div class=""><br class="">
</div>
<div class="">A -1 from a third party CI tool can often be an indication that the CI tool itself or the third party plugin is broken, rather than there being issues with the patch under review. I don’t think there are many cases where a third party CI tool has caught
a genuine issue that Jenkins has missed. With the current voting rights these CI tools cause a lot of noise when they experience problems.</div>
<div class=""><br class="">
</div>
<div class="">I’m not suggesting that the results of these tests be removed from the page altogether - there are some cases where their results are useful to the patch author/reviewer - but removing voting rights (or at least -1 rights) would save a patch from a –1
that might not be particularly meaningful.</div>
<div class=""><br class="">
</div>
<div class="">Thoughts?</div>
<div class=""><br class="">
</div>
<div class="">John</div>
</div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>