<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>I think this make sense. I have lost any faith on third party CIs after the Vancouver decision of not police them (I was doing that for a while and I was fine doing it). So, why to keep them with voting rights? I will say, let’s remove voting rights for
all of them. </div>
<div><br>
</div>
<div>Edgar</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"John Davidge (jodavidg)"<br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)"<br>
<span style="font-weight:bold">Date: </span>Thursday, June 25, 2015 at 7:08 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)"<br>
<span style="font-weight:bold">Subject: </span>[openstack-dev] [openstack-infra] [neutron] Third Party CI Voting<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi all,</div>
<div><br>
</div>
<div>Recent neutron third party CI issues have got me thinking again about a topic which we discussed in Vancouver:</div>
<div><br>
</div>
<div>Should any Third Party CI have voting rights for neutron patches in gerrit?</div>
<div><br>
</div>
<div>I’d like to suggest that they shouldn’t.</div>
<div><br>
</div>
<div>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><br>
</div>
<div>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><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>John</div>
</div>
</div>
</span>
</body>
</html>