[openstack-dev] [openstack-infra] [neutron] Third Party CI Voting

Edgar Magana edgar.magana at workday.com
Thu Jun 25 15:06:42 UTC 2015

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.


From: "John Davidge (jodavidg)"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, June 25, 2015 at 7:08 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [openstack-dev] [openstack-infra] [neutron] Third Party CI Voting

Hi all,

Recent neutron third party CI issues have got me thinking again about a topic which we discussed in Vancouver:

Should any Third Party CI have voting rights for neutron patches in gerrit?

I’d like to suggest that they shouldn’t.

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.

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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150625/6021d01a/attachment.html>

More information about the OpenStack-dev mailing list