Not sure if this is the right repo.
Could you please support Zuul on Pull Requests to the fc35 branches?
Example:
https://src.fedoraproject.org/rpms/pypy3/pull-request/28
Thanks.
@fbo is the procedure to add a new fedora version already documented somewhere?
@tdecacqu well no.
So here it is (+ definition of f35 branch): - https://pagure.io/fedora-project-config/pull-request/155
Plus the required changes into fedora-zuul-jobs-config and fedora-zuul-jobs: - https://pagure.io/fedora-zuul-jobs-config/pull-request/131 - https://pagure.io/fedora-zuul-jobs/pull-request/119
@tdecacqu please review
This has all been merged, but f35 PRs still fail with:
error: the requested upstream branch 'origin/f35' does not exist
See e.g. https://fedora.softwarefactory-project.io/zuul/build/2f4ad0f5f79442659c7341b4aeb9d567 from https://src.fedoraproject.org/rpms/python3.9/pull-request/81
@churchyard Sorry for the late reply (I was on PTO) so looking now
it seems the Zuul copy of the repo + pr to the test node missed the origin/f35 ref to satisfy the fedpkg srpm command. That's probably a bug in zuul side and a wipe of the repos cached on the Zuul server might have helped. However to avoid this I've merged a small change in zuul-distro-jobs to force the local copy to have that origin refs. This fix seems to be ok in my tests.
Please reopen if you see any issues.
Metadata Update from @fbo: - Issue status updated to: Closed (was: Open)
Are the arched scratch builds fixed as well? Here https://src.fedoraproject.org/rpms/python3.7/pull-request/32#comment-84625 it seems only x86_64 was fixed. Restarted and will reopen here if I see the same issue.
Arched scratch builds use the same process to build the srpm so they should be fixed as well. I see the last recheck was a success. So it seems we are ok.
Yes indeed. Thanks again!
Login to comment on this ticket.