Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/dc30dd3f7bac42a9a2a73fab276df202

• config-check : SUCCESS in 33s

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/e3a0ff1851764500a584ac4d8400da42

• config-check : SUCCESS in 30s

sigh, it looks like SF didn't quite add f42 container definitions yet?! there's some bits from fd846c2b8a1edb60164357d19fae6e9fcfdae7b8 "Update zuul-worker-dhall and install pyyaml" in June, but there's no zuul.d/zuul-worker-f42.dhall.

Also zuul.d/zuul-worker-fedora-stable.dhall is still pointing to F40, which went EOL months ago. I guess that's probably why fedora-comps CI jobs are still running in an F40 container (and thus failing).

Trimmed to only add F43 VM definitions, and get rid of all F40.

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/0764135de45f4a979df59b8f6c4ed67d

• config-check : SUCCESS in 51s

• fedora-zuul-jobs PR
• fedora-zuul-jobs-config PR

zuul-worker-fedora-stable.dhall

Might not be used. Any reference for the fedora-comps CI jobs? But I guess this is not touched in the latest rebase anyway?

Aren't there SF changes needed to provide the F43 workers? Probably the generated PRs complain if that part is misconfigured, don't quite remember.

One comment on the fedora-zuul-jobs-config generated PR, it seems it was run on an older branch? Other than that LGTM

I got the softwarefactory stuff done in https://softwarefactory-project.io/r/c/containers/+/34599 and https://softwarefactory-project.io/r/c/containers/+/34600 , and that's actually fixed the pungi-fedora (it was pungi-fedora, not fedora-comps, I misremembered) CI jobs already. But we should still do this.

Now we got F42 and F43 added to SF, in fact, I'll revise this back to adding 42 and 43 containers here as well, and re-gen the child PRs.

Thanks for the reference and the work on those. Just the minor generation issue remaining (might be I missed some dhall stuff on my side when I did that PR there?).

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/f2a2fff79b3a479eb59f4674c9c34f82

• config-check : SUCCESS in 32s

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/2e1e3a985f184827a93c06bee57a66f8

• config-check : SUCCESS in 30s

So I redid this again to include F42 and F43 containers. It's also a bit more 'opinionated' as it bumps all the 'generic' tasks that were using F41 containers to use F42 containers; if there's a potential problem with that, I can change it back, I guess. I also changed a case which was explicitly using Fedora-41-Container to use Fedora-Latest-Container instead, because there was no indication that it was pinned to 41 for a specific reason, so why have another 'touch point' when bumping versions? Again, let me know if there's an issue with that.

btw, wouldn't this all be much easier and more automatable if we had a few variables ('current fedora releases', 'development fedora releases', 'current stable fedora release') and used them, instead of just hardcoding the numbers in a dozen+ different places? Then we'd only need to update the variables when Fedora releases branch, go EOL, or go stable...

btw, wouldn't this all be much easier and more automatable if we had a few variables

Yes, but would not be much worth it. I am preparing the announcement for the change of the zuul runner to packit Fedora-CI for next week. Ideally we would have a trial to get some feedback, and depending on how that goes we can see how we should move on with any QOL improvements.

Final LGTM on this. Maybe have @fab give a quick look over too? Otherwise I would leave it to you to merge them?

Note for @fab, there is a small hiccup with the Zuul.dhall not being able to add post-run jobs as dict items (for cleanup). I want to deffer this to see if we would really need it for the long run.

I can't merge anything, I don't have commit rights to these projects.

Ping? Can we please get this and the child requests merged? fedora-latest-container still points to F41 ATM, which is supposed to be EOL as of yesterday.

Actually I guess I should update this to make F43 'latest', since it's now stable.

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/83a2b8edf0fd4e61b509f9954024064b

• config-check : SUCCESS in 33s

Updated this and the child PRs to make F43 'latest'.

I can't merge anything, I don't have commit rights to these projects.

Sorry, I meant to come back to this and merge it if there was no further updates. I'll do one more check and go forward with it. Also https://pagure.io/fedora-ci/general/issue/534 is relevant, would want to go through with it asap.

ping again @lecris ?

Just needs https://pagure.io/fedora-zuul-jobs-config/pull-request/209#comment-226231 adressing

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/f643b40370d84b68aef90d574bdc27b3

• config-check : SUCCESS in 32s

OK, this and the child PRs are now rebased and updated to drop F41 as well as F40, as F41 is also now EOL.

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/0e549ec0211044509bbf0c7b5319f2b3

• config-check : SUCCESS in 32s

:thumbsup: other than waiting for more :eyes: on the fedora-zuul-jobs

Build succeeded (gate pipeline).
https://fedora.softwarefactory-project.io/zuul/buildset/e212e02273f04c8eb80319aafe3421fb

• config-check : SUCCESS in 32s

Seems like the Zuul jobs are not running https://fedora.softwarefactory-project.io/zuul/status. I suspect this is an issue deeper in the zuul infra

oh good I broke stuff? yay.

Seems like it was from the quay.io image being private. It is fixed now