@@ -78,10 +78,10 @@ The automation is achieved via the [autopatch_release](https://gitlab.cern.ch/li
4. the `.src.rpm` from the branch `{branch}_newrelease` (or `srpms` if `{branch_proposed} exists) is installed to a temporary location
5. the CERN version of the release is cloned and a the branch `{branch}_proposed` is checked out (created if it does not already exist)
6. the `.src.rpm` is committed as well into git into a `srpms` directory. This step is necessary if autopatch release is executed multiple times as autopatch needs the upstream spec file to perform processing
7. comparision between the .src.rpm `SOURCES` and git `src` is made, if there are any differences - they are copied into place
7. comparison between the .src.rpm `SOURCES` and git `src` is made, if there are any differences - they are copied into place
- Note - `.repo` and `.spec` files are deliberately excluded for branches that already exist
- In the event of a completely new release (eg: almalinux-release-11), the .spec files are copied without modification as the expectation is that the admins will modify them before merge
8. The AlmaLinux autopatch tool is executed to make modifcations to the `.spec` file. A custom wrapper `almalinux-autopatch-wrapper.py` exists to run this command via the CLI
8. The AlmaLinux autopatch tool is executed to make modifications to the `.spec` file. A custom wrapper `almalinux-autopatch-wrapper.py` exists to run this command via the CLI
9. Changes are committed to git and then pushed via the `{branch}_proposed` branch. The push also includes the creation of a merge request (if one does not already exist)
10. The MR URL is emailed to administrators to action
...
...
@@ -97,7 +97,7 @@ To add support for a completely new release (eg: `almalinux-release-11`) the fol
3) add `autopatch_release/configs/almalinux-release_a11.yaml` to do stuff
4) ran `autopatch_release`
5) If additional configuration is required, add more configuration to config file (repeat steps #3 and #4)
6) For completely new release files, `autopatch_release` will add the upsteam `.repo` files, these will need to be modified to reference the CERN urls before the MR is merged
6) For completely new release files, `autopatch_release` will add the upstream `.repo` files, these will need to be modified to reference the CERN urls before the MR is merged
7) It would be useful at this point to also update the "feeds" defined in [package_alerts](https://gitlab.cern.ch/linuxsupport/cronjobs/package_alerts) so that future `almalinux-release` src.rpms are automatically added to the `a11_newrelease` branch
