On 9/20/24 9:11 AM, Brian Rosmaita <rosmaita.fossdev@gmail.com> wrote:
Hello Unmaintained maintenance team,
I was reviewing a cinder-tempest-plugin patch (which is in an un- branched repository), and noticed that we have a bunch of Zuul cinder jobs defined for stable branches that no longer exist, for example, stable/wallaby [0].
Where this impacts the unmaintained branches is that, for example, unmaintained/wallaby's .zuul.yaml is configured to run (for example) cinder-tempest-plugin-lvm-lio-barbican in the check [1], but you can see on this review, it's not actually running:
https://review.opendev.org/c/openstack/cinder/+/926279?tab=change-view- tab-header-zuul-results-summary
So, my question is what to do about these unused jobs:
(a) delete them
(b) only delete stable/x for x <= ussuri, and update the jobs for stable/x for victoria <= x <= zed to unmaintained/x
(c) delete them all, but propose a patch to the appropriate unmaintained branches zuul.yaml files that contain the job definition so that the Unmaintained team can make any changes needed to get them running without having to go through the cinder-tempest-plugin-core team's review/approval process
This sounds like the best path to me, but I'm not an incredibly active member of the unmaintained unmaintainence unteam so I'm happy to go with whatever others think if there is disagreement. -Jay Faulkner
(d) something I haven't thought of
Thanks! brian
[0] https://opendev.org/openstack/cinder-tempest-plugin/src/branch/ master/.zuul.yaml#L170 [1] https://opendev.org/openstack/cinder/src/branch/unmaintained/ wallaby/.zuul.yaml#L68