It appears the Zuul doe snot start for f36 PRs, e.g. in https://src.fedoraproject.org/rpms/python-rpm-generators/pull-request/54
Could you please make it run? You might need to use a rawhide base image until an f36 one exists.
Metadata Update from @fbo: - Issue tagged with: Zuul CI
seems it run, was it just delayed @fbo
I don't see it run. The green Zuul badge is coming from the rawhide PR from the same commit.
@churchyard oh wow, that is so confusing I see it just now, some note about what target is used would be nice next to the name. So Zuul should be there also twice as poor Fedora CI ...
Yes, I feel it confusing as well and it looks like to be Pagure issue.
Anyway here are the changes for the f36 support. I'll wait for @tdecacqu to get it approved.
Feel free to have a look, I'll be happy to get reviewes/comments on it :)
I looked, looks clean to me. Fedora-36 is available in Testing Farm:
https://api.dev.testing-farm.io/v0.1/composes
So I am fine merging it and trying out.
I see it just now, some note about what target is used would be nice next to the name.
Yes, I have opened https://pagure.io/fedora-ci/general/issue/236 10 months ago.
Yes, I have opened and commented https://pagure.io/pagure/issue/5104#comment-713920 a year ago.
:( commented on that issue
Thank you @fbo, the changes look great. I think we can simplify the process by moving all the branch name rendering to the project-config, so that in the future, only one change needs to be made, and just run make on the three projects. Is there an existing documentation to add CI support for a new fedora branch?
Thanks for the review. @tdecacqu no, there's no documentation beside the previous PRs for the previous branches support. Yes perhaps all Dhall files should be inside only one repo. Once we reach that point then maybe we could document in the wiki page.
@churchyard @mvadkert PRs are merged. Support should be there now. I'm closing the issue. Please re-open if needed.
Metadata Update from @fbo: - Issue status updated to: Closed (was: Open)
Thank you!
Login to comment on this ticket.