On Thu, Aug 6, 2020 at 5:19 PM Sergii Golovatiuk <sgolovat at redhat.com> wrote: > Hi, > > tripleo-ci-centos-8-containerized-undercloud-upgrades has been improved > significantly in terms of stability [1]. To improve CI coverage for > upgrades I propose to make it voting. That will help to make upgrades more > stable and catch bugs as early as possible. To keep it stable, Upgrade team > is going to add it to their own triage process and dedicate the engineer to > fix it if it's red for 2-3 days in a row. > > o/ as discussed on irc, IMO we should make it voting "until we can't". Your triage process about 2/3 days sounds reasonable but it will be seen in practice how well that works. Which is the original reason there is push-back against master voting upgrades jobs - i.e. whilst developing for the cycle the upgrades jobs might break until all new features are merged and you can accommodate for them in the upgrade. So they break and this blocks master gates. They were made non voting during a time that they were broken often and for long periods. let's make them voting "until we can't". > [1] > https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-8-containerized-undercloud-upgrades&project=openstack/tripleo-common > > -- > Sergii Golovatiuk > > Senior Software Developer > > Red Hat <https://www.redhat.com/> > <https://www.redhat.com/> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200806/78e2a784/attachment-0001.html>