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

Marios Andreou marios at redhat.com
Tue Feb 9 17:03:58 UTC 2021

On Tue, Feb 9, 2021 at 6:46 PM Jesse Pretorius <jesse at odyssey4.me> wrote:

> On 9 Feb 2021, at 16:29, Wesley Hayutin <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 )
> tripleo-ci-centos-8-standalone-upgrade
> tripleo-ci-centos-8-undercloud-upgrade
> tripleo-ci-centos-8-scenario000-multinode-oooq-container-upgrades
> 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.

just to be clear however, note that this means that there will be no
stable/wallaby version of these upgrades jobs, or at least it will be a lot
harder to add them if we aren't running these jobs against master. In the
'normal' case, the non-voting master jobs become the voting stable/latest
once we have created the new latest branch. If we remove master we may have
a challenge to add voting stable/wallaby versions when the time comes.

Based on our recent discussions, we don't *want* stable/wallaby versions
since we want to eventually remove all the upstream upgrade jobs once
d/stream replacements have been put in place.

The point then is that ideally we need to be in a position to do that (i.e.
replacement jobs in place) before stable/wallaby is branched, otherwise we
may have a tough time adding stable/wallaby versions of the (removed)
master upgrade jobs.

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

More information about the openstack-discuss mailing list