Hello. In the upcoming weeks, we will do a mass Python 3.9 rebuild for https://fedoraproject.org/wiki/Changes/Python3.9
The rebuild will happen in a side tag. After we push the bump commit, we do fedpkg build --target=f33-python --background not to overload Koji.
fedpkg build --target=f33-python --background
I like to use this ticket to coordinate this, so Zuul does not immediately start building the packages in the regular target. What can be done? Do we temporarily disable all publish jobs?
Thanks.
Hi,
Yes sure. So I'm not really aware of the exact process of mass rebuild ...
So do you expect that scratch build performed by Zuul for master branch and python packages use by default f33-python instead of rawhide ? We could use the target var to set the correct build target for specific packages. https://pagure.io/fedora-zuul-jobs-config/blob/master/f/zuul.d/jobs.yaml#_34
We don't have so much python packages with the publish job configured in Zuul. So we could disable them temporarily by removing the publish template (https://pagure.io/fedora-zuul-jobs-config/blob/master/f/zuul.d/projects.yaml#_77)
So do you expect that scratch build performed by Zuul for master branch and python packages use by default f33-python instead of rawhide ?
Not really. I just need to temporarily disable the automation for "publish" for them.
So we could disable them temporarily by removing the publish template
This works for me best.
https://pagure.io/fedora-zuul-jobs-config/pull-request/58
Progress info: python-ws4py is blocked, everything else was built.
Metadata Update from @churchyard: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.