Infrastructure/infra-docs-fpo
3
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Add manual koji steps to the SOP

Browse source
This commit is contained in:
Diego Herrera 2025-03-10 14:21:08 -03:00
parent b80b4a83bf
commit f901165fbe
1 changed files with 23 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

28
modules/release_guide/pages/sop_epel_minor_mass_branching.adoc
View file

@ -9,13 +9,20 @@ Originally, the EPEL repository had packages that built against the latest RHEL
== Send announcement == Send announcement
One day before the mass branching, we send out announcement because during mass branching, One day before the mass branching, we send out announcement because during mass branching,
new koji builds for EPEL are disabled. This will imply a koji outage in Fedora too. new koji builds for EPEL are disabled.
=== Remove Targets
[NOTE]
====
In Fedora it is recommended to https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_disable_rawhide_builds_in_koji[stop connections to koji through firewall]. In Fedora it is recommended to https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_disable_rawhide_builds_in_koji[stop connections to koji through firewall].
But it was https://pagure.io/infra-docs-fpo/pull-request/357[decided not to require it] for this process. But it was https://pagure.io/infra-docs-fpo/pull-request/357[decided not to require it] for this process.
====
In the case of EPEL, just removing the targets is enough to disable it's usage for the time being while the branching process it's being done.
[source,bash,subs="attributes"]
----
$ koji remove-target epel10-candidate
$ koji remove-target epel10
----
=== Cancel all running build for EPEL{epel_major} === Cancel all running build for EPEL{epel_major}
@ -57,7 +64,7 @@ On `pkgs01.stg` (for testing) or `pkgs02` (for production), run:
[source,bash,subs="attributes"] [source,bash,subs="attributes"]
---- ----
$ sudo -u pagure python /usr/local/bin/mass-branching-git.py epel{epel_current} components_epel{epel_major}.txt epel{epel_major} $ sudo -u pagure python /usr/local/bin/mass-branching-git.py --branch-from epel{epel_major} epel{epel_current} components_epel{epel_major}.txt
---- ----
The first argument is the new epel version and the The first argument is the new epel version and the
@ -190,6 +197,17 @@ $ sudo rbac-playbook openshift-apps/bodhi.yml
$ sudo systemctl restart fm-consumer@config.service bodhi-celery.service $ sudo systemctl restart fm-consumer@config.service bodhi-celery.service
``` ```
=== Recreate targets
Once mass-branching is complete and the new release exists in bodhi,
re-create these targets with the following commands:
[source,bash,subs="attributes"]
----
$ koji add-target epel${release_major} epel${release}-build epel${release}-testing-candidate
$ koji add-target epel${release_major}-candidate epel${release}-build epel${release}-testing-candidate
----
=== Update block_retired.py script === Update block_retired.py script
https://pagure.io/releng/blob/main/f/scripts/block_retired.py[block_retired.py] https://pagure.io/releng/blob/main/f/scripts/block_retired.py[block_retired.py]