Tagging a release: 2021-05-10
- In foreman 2.5-stable:
- Make sure test_2_5_stable is green
-
runmake -C locale tx-update
-
Tag the release using tag.sh
tag.sh 2.5.0-rc2 && git push upstream 2.5-stable --follow-tags
- In smart-proxy 2.5-stable:
- Make sure test_proxy_2_5_stable is green
-
Tag the release using tag.sh
tag.sh 2.5.0-rc2 && git push upstream 2.5-stable --follow-tags
- In foreman-selinux 2.5-stable:
-
Tag the release using tag.sh
tag.sh 2.5.0-rc2 && git push upstream 2.5-stable --follow-tags
-
Tag the release using tag.sh
- In foreman-installer 2.5-stable:
-
Tag the release using tag.sh
tag.sh 2.5.0-rc2 && git push upstream 2.5-stable --follow-tags
-
Tag the release using tag.sh
- Run the Jenkins Tarballs Release to create tarballs
- Update release version similar to here
- Sign Tarballs
Note: If for some reason there was an issue with the tarballs that required uploading new tarballs, CDN cache should be invalidated so that the builders use the updated tarballs.
Packaging a release: 2021-05-10
- Update foreman-packaging
- Trigger release_packages in Jenkins by calling release_packages script.
-
Tag
foreman-release
intoforeman-client-2.5-rhel7
andforeman-client-2.5-el8
, as this doesn’t happen automatically for those tags. Make sure the build matches the release.-
koji tag-build foreman-client-2.5-rhel7 foreman-release-2.5.0-1.el7
-
koji tag-build foreman-client-2.5-el8 foreman-release-2.5.0-1.el8
-
- Check for outstanding PRs against 2.5 packaging, and merge if possible:
- Sign the RPMs in the release
-
Sign RPMs for client repos (call scripts with
PROJECT=client
) -
Kick off the release pipeline by calling
release_pipeline
-
Kick off the client pipeline by calling
PROJECT=client release_pipeline
- Kick off the plugins pipeline by calling plugins_pipeline
After the packages have been released
- Announce the release on Discourse
- Update the topic in #theforeman channel on Freenode
- Share the release announcement on twitter
- Release pipeline will trigger foreman-plugins-2.5-deb-test-pipeline and foreman-plugins-2.5-rpm-test-pipeline. These don’t block releases but can be used to understand known issues around plugin compatibility with Foreman 2.5.