[openstack-dev] [tripleo] reducing our upstream CI footprint
whayutin at redhat.com
Wed Oct 31 17:39:59 UTC 2018
On Wed, Oct 31, 2018 at 11:21 AM Alex Schultz <aschultz at redhat.com> wrote:
> Hey everyone,
> Based on previous emails around this, I have proposed a possible
> reducing in our usage by switching the scenario001--011 jobs to
> non-voting and removing them from the gate. This will reduce the
> likelihood of causing gate resets and hopefully allow us to land
> corrective patches sooner. In terms of risks, there is a risk that we
> might introduce breaking changes in the scenarios because they are
> officially non-voting, and we will still be gating promotions on these
> scenarios. This means that if they are broken, they will need the
> same attention and care to fix them so we should be vigilant when the
> jobs are failing.
> The hope is that we can switch these scenarios out with voting
> standalone versions in the next few weeks, but until that I think we
> should proceed by removing them from the gate. I know this is less
> than ideal but as most failures with these jobs in the gate are either
> timeouts or unrelated to the changes (or gate queue), they are more of
> hindrance than a help at this point.
I think I also have to agree.
Having to deploy with containers, update containers and run with two nodes
is no longer a very viable option upstream. It's not impossible but it
should be the exception and not the rule for all our jobs.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
whayutin at redhat.com T: +1919 <+19197544114>4232509 IRC: weshay
View my calendar and check my availability for meetings HERE
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev