[openstack-dev] [infra] Try to introduce RFC mechanism to CI.

Znoinski, Waldemar waldemar.znoinski at intel.com
Fri Oct 9 15:19:07 UTC 2015

 >-----Original Message-----
 >From: Jeremy Stanley [mailto:fungi at yuggoth.org]
 >Sent: Friday, October 9, 2015 1:17 PM
 >To: OpenStack Development Mailing List (not for usage questions)
 ><openstack-dev at lists.openstack.org>
 >Subject: Re: [openstack-dev] [infra] Try to introduce RFC mechanism to CI.
 >On 2015-10-09 18:06:55 +0800 (+0800), Tang Chen wrote:
 >> It is just a waste of resource if reviewers are discussing about where
 >> this function should be, or what the function should be named. After
 >> all these details are agreed on, run the CI.
[WZ] I'm maintaining 2 3rdparty CIs here, for Nova and Neutron each, and to me there's no big difference in maintaining/supporting a CI that runs 5 or 150 times a day. The only difference may be in resources required to keep up with the Gerrit stream. In my opinion (3rdparty) CIs should help early-discover the problems so should run on all patchsets as they appear - that's their main purpose to me.

 >As one of the people maintaining the upstream CI and helping coordinate our
 >resources/quotas, I don't see that providing early test feedback is a waste.
 >We're steadily increasing the instance quotas available to us, so check
 >pipeline utilization should continue to become less and less of a concern
 >For a change which is still under debate, feel free to simply ignore test results
 >until you get it to a point where you see them start to become relevant.
 >Jeremy Stanley
 >OpenStack Development Mailing List (not for usage questions)
 >Unsubscribe: OpenStack-dev-
 >request at lists.openstack.org?subject:unsubscribe
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

More information about the OpenStack-dev mailing list