[tripleo][ci] socializing upstream job removal ( master upgrade, scenario010 )

Jesse Pretorius jesse at odyssey4.me
Tue Feb 9 16:45:01 UTC 2021

On 9 Feb 2021, at 16:29, Wesley Hayutin <whayutin at redhat.com<mailto:whayutin at redhat.com>> wrote:

Upgrade jobs in master:
All the upgrade jobs in master are non-voting based on policy and to give the upgrade developers time to compensate for new developments and features.   The feedback provided by CI can still occur in our periodic jobs in RDO's software factory zuul.   Upgrade jobs will remain running in periodic but removed from upstream.

Specifically:  ( master )

I'll note there is interest in keeping the undercloud-upgrade, however we are able to remove all the upgrade jobs for a branch in the upstream we can also remove a content-provider job.  I would encourage folks to consider undercloud-upgrade for periodic only.

+1 I think this makes sense. These jobs are long running and consume quite a few VM over that lengthy period of time.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210209/1bfcf629/attachment-0001.html>

More information about the openstack-discuss mailing list