Hi,
Today I got back to checking my old patches which are going to fix some zuul jobs' definitions.
And I found that CI for networking-midonet in some stable branches is totally broken:
* stable/ussuri: https://review.opendev.org/c/openstack/networking-midonet/+/823273[1] - everything is red here
* stable/train: https://review.opendev.org/c/openstack/networking-midonet/+/823275[2] - most of the jobs are red
* stable/stein: https://review.opendev.org/c/openstack/networking-midonet/+/823276[3] - here there were errors in the definition of the jobs, I changed it now, maybe it will run,
So my question is if we want, and have resources, to fix it somehow or should we maybe set those branches as EOL now?
Also, another question to the Zuul team - will it be ok if such branch will be EOL to get rid of the Zuul configuration errors warnings? Or should we somehow force to merge those patches first to get rid of the errors in https://zuul.opendev.org/t/openstack/config-errors[4] ?
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
--------
[1] https://review.opendev.org/c/openstack/networking-midonet/+/823273
[2] https://review.opendev.org/c/openstack/networking-midonet/+/823275
[3] https://review.opendev.org/c/openstack/networking-midonet/+/823276
[4] https://zuul.opendev.org/t/openstack/config-errors
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220411/51c5f587/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220411/51c5f587/attachment.sig>