Update mass branching document for more details
Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
This commit is contained in:
parent
e71562063e
commit
475e4023ad
1 changed files with 74 additions and 12 deletions
|
@ -60,9 +60,43 @@ On branching day, remove the robosignatory config for this resigning.
|
|||
One day before the mass branching, we send out announcemt because during mass branching,
|
||||
new koji builds for rawhide are disabled.
|
||||
|
||||
== Create Bugzilla Component
|
||||
|
||||
To ensure accurate tracking and management of issues for each Fedora release, a new Bugzilla component should be created for the branched version, as this step is currently not covered in the documentation. A user with access to the 'fedora-pm' Bugzilla group needs to perform the following actions:
|
||||
|
||||
* Log in to Bugzilla.
|
||||
* Navigate to the "Administration" section.
|
||||
* Under "Components," locate "Fedora."
|
||||
* Select "Edit Versions" to view the existing components.
|
||||
* Add the new branched version to the list.
|
||||
|
||||
This process allows for proper issue categorization and ensures all bugs related to the new Fedora release are properly tracked.
|
||||
|
||||
== Disable rawhide builds in koji
|
||||
|
||||
We need to configure outage in koji. Look at https://pagure.io/fedora-infra/ansible/pull-request/1528[this PR]
|
||||
|
||||
Previously, disabling all builds in Koji involved configuring an outage as demonstrated in this pull request. However, starting with the Fedora 41 release, the approach was refined to block external submissions in Koji by setting a custom IP restriction.
|
||||
|
||||
The recommended method to achieve this is by adding firewall rules to both koji01 and koji02 servers, effectively blocking connections from proxy01 and proxy10. This can be achieved with the following iptables commands:
|
||||
|
||||
[source,bash,subs="attributes"]
|
||||
----
|
||||
iptables -I INPUT -m tcp -p tcp --dport 80 -s proxy01.iad2.fedoraproject.org -j REJECT
|
||||
iptables -I INPUT -m tcp -p tcp --dport 80 -s proxy10.iad2.fedoraproject.org -j REJECT
|
||||
----
|
||||
|
||||
These commands reject incoming traffic on port 80 from the specified proxies, preventing external submissions. Internal connections routed via proxy101 and proxy110 will continue to function as expected.
|
||||
|
||||
To reverse the firewall changes and allow external submissions again, use:
|
||||
|
||||
[source,bash,subs="attributes"]
|
||||
----
|
||||
iptables -D INPUT -m tcp -p tcp --dport 80 -s proxy01.iad2.fedoraproject.org -j REJECT
|
||||
iptables -D INPUT -m tcp -p tcp --dport 80 -s proxy10.iad2.fedoraproject.org -j REJECT
|
||||
|
||||
----
|
||||
|
||||
This change should be implemented on both koji01 and koji02 machine.
|
||||
|
||||
=== Cancel all running build for rawhide
|
||||
|
||||
|
@ -175,6 +209,26 @@ infra ansible repo. This change includes, updating `koji-sync-listener.py`,
|
|||
|
||||
Please check these files from the https://pagure.io/fedora-infra/ansible/c/549e5d3ace41c04fdbef9d81f359f16c2fe0c2fa?branch=main[commit] for your reference.
|
||||
|
||||
== Releng updates
|
||||
|
||||
=== Update sync script
|
||||
|
||||
In releng repository update
|
||||
https://pagure.io/releng/blob/main/f/scripts/sync-latest-container-base-image.sh#_38[script].
|
||||
|
||||
And set current_rawhide variable.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Hopefully someday soon this will be in cloud-image-uploader!
|
||||
====
|
||||
|
||||
== Toddlers
|
||||
|
||||
=== Add new SLA to the toddlers App
|
||||
|
||||
Use https://pagure.io/fedora-infra/ansible/pull-request/1527[this PR] for reference and add new version to the config.
|
||||
|
||||
=== Enable Branched Compose
|
||||
|
||||
We need to enable the branched compose. This is done in
|
||||
|
@ -403,6 +457,11 @@ Build `fedora-release` and `fedora-repos` packages for Branched release
|
|||
*before enabling the Rawhide gating*.
|
||||
====
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Consider using sidetags for `fedora-release` and `fedora-repos` updates; these updates should be bundled with updates to `mock-core-configs` and `distribution-gpg-keys` for a unified push.
|
||||
====
|
||||
|
||||
Changes to the *stable* branches (mostly in `fedora-repos.spec`):
|
||||
|
||||
[arabic]
|
||||
|
@ -465,12 +524,18 @@ from https://pagure.io/releng[pagure releng] repo. This should be run on
|
|||
$ sudo -u ftpsync sh scripts/branching/create_empty_repos.sh {branched}
|
||||
----
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Update the link in /mnt/koji/repos/rawhide/latest as per https://pagure.io/releng/issue/12255.
|
||||
====
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
Please verify the repo permissions that are created under
|
||||
/pub/fedora/linux/development/<fedora_release_number> and
|
||||
/pub/fedora-secondary/development/<fedora_release_number>. They should
|
||||
be owned by _ftpsync:ftpsync_
|
||||
Check directory permissions (should be "0755") to ensure new composes synchronize correctly.
|
||||
====
|
||||
|
||||
=== Creating rawhide release
|
||||
|
@ -643,18 +708,15 @@ Untagged: fedora-docker-base-rawhide-20170310.n.0.x86_64:latest
|
|||
$ for i in $(sudo docker images -q -f 'dangling=true'); do sudo docker rmi $i; done
|
||||
----
|
||||
|
||||
=== Update sync script
|
||||
[NOTE]
|
||||
====
|
||||
Temporarily disable the rawhide cron job during branching PRs to ensure a branched compose is created. Re-enable rawhide after this.
|
||||
====
|
||||
|
||||
In releng repository update
|
||||
https://pagure.io/releng/blob/main/f/scripts/sync-latest-container-base-image.sh#_38[script].
|
||||
|
||||
And set current_rawhide variable.
|
||||
|
||||
== Toddlers
|
||||
|
||||
=== Add new SLA to the toddlers App
|
||||
|
||||
Use https://pagure.io/fedora-infra/ansible/pull-request/1527[this PR] for reference and add new version to the config.
|
||||
[NOTE]
|
||||
====
|
||||
In fedora-repos package build for new branched version enable the update-testing repository immediately upon branching.
|
||||
====
|
||||
|
||||
== Consider Before Running
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue