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

sop_mass_branching: Remove PDC and update koji blocking section

Browse source 
Signed-off-by: Lenka Segura <lsegura@redhat.com>
This commit is contained in:
Lenka Segura 2024-12-03 12:49:50 +01:00 • committed by jnsamyak
parent 9c01f10369
commit c9573f5621
1 changed files with 7 additions and 53 deletions
Download patch file Download diff file Expand all files Collapse all files

60
modules/release_guide/pages/sop_mass_branching.adoc
View file

@ -128,52 +128,10 @@ values.
* https://src.fedoraproject.org/rpms/fedora-release * https://src.fedoraproject.org/rpms/fedora-release
* https://src.fedoraproject.org/rpms/fedora-repos * https://src.fedoraproject.org/rpms/fedora-repos
== PDC
The "product-release" needs to be created in PDC.
In the `scripts/pdc/` directory, run:
```
$ python create-product-release.py fedora $TOKEN Fedora $NEW_VERSION
```
On `pdc-backend01.stg` (for testing) or `pdc-backend01` (for production)
clone (or update an existing one) the releng repo:
```
$ git clone https://pagure.io/releng.git
```
In the `scripts/pdc/` directory, run (see the `--help` of the script for
information on how to run it):
```
$ python create-new-release-branches.py ... --createfile
```
NOTE: The `--createfile` argument is necessary, that file is needed for the next step.
[NOTE]
====
Due to memory leak issue in pdc, we need to set the config in
`/etc/pdc.d/fedora.json`:
```
{
"fedora":
{
"host": "http://pdc-web02.iad2.fedoraproject.org/rest_api/v1/",
"develop": false,
"ssl-verify": false
}
}
```
====
== dist-git == dist-git
Now that pdc has the new release and each package has been branched in Now we need to update dist-git in two steps:
pdc we need to update dist-git in two steps:
* Create the new branch in git * Create the new branch in git
* Update the gitolite.conf to allow user to push to this new branch * Update the gitolite.conf to allow user to push to this new branch
@ -182,7 +140,7 @@ For both of these actions you will need the file generated by pdc above.
=== Create the git branches === Create the git branches
On `pkgs01.stg` (for testing) or `pkgs02` (for production), run: On `pkgs01.stg` (for testing) or `pkgs01` (for production), run:
``` ```
$ sudo -u pagure python /usr/local/bin/mass-branching-git.py <new branch name> <input file> $ sudo -u pagure python /usr/local/bin/mass-branching-git.py <new branch name> <input file>
@ -603,15 +561,11 @@ $ rm -f latest
$ ln -s ../f{rawhide}-build/latest ./latest $ ln -s ../f{rawhide}-build/latest ./latest
---- ----
=== Update block_retired.py script === Make sure branched release does not have set EOL
Presence/absence of EOL date is the way the
https://pagure.io/releng/blob/main/f/scripts/block_retired.py[block_retired.py] https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/koji_block_retired.py[toddler
script in releng repo should be updated with rawhide release and also koji_block_retired] distinguishes between stable and branched releases. EOL should be filled
branched release should be added to the script. once a release becomes stable.
Please look at this
https://pagure.io/releng/c/9eb97f491f7a767ab8b90498adfa3b34ee235247?branch=main[block_retired.py
commit] as an example.
=== Updating MirrorManager === Updating MirrorManager