Foreman 1.23.2 release procedure

[tbrisker]

Make this post a wiki

Manual updates

• Update release notes section in the manual:
  • Release notes: bullet point list by category of all changes, include link to bug numbers. You can auto-generate changes using the release notes script.

Preparing code

• Compare tagged packages in nightly vs. release koji tag and re-tag any updated dependencies that are required
• Remove/change release field for any open Redmine tickets assigned to the release still (next minor, unset it or reject)
• Change Redmine version 1.23.2 state to Closed
• Ensure that code in git matches issues fixed in 1.23.2 in redmine. issues.rb can be used to generate a comparison between the two.

Tagging a release

• In foreman 1.23-stable:
  • Make sure test_1_23_stable is green
  • Tag the release using tag.sh tag.sh 1.23.2
  • Push: git push upstream 1.23-stable --follow-tags
• In smart-proxy 1.23-stable:
  • Make sure test_proxy_1_23_stable is green
  • Tag the release using tag.sh tag.sh 1.23.2
  • Push: git push upstream 1.23-stable --follow-tags
• In foreman-selinux 1.23-stable:
  • Tag the release using tag.sh tag.sh 1.23.2
  • Push: git push upstream 1.23-stable --follow-tags
• In foreman-installer 1.23-stable:
  • Tag the release using tag.sh tag.sh 1.23.2
  • Push: git push upstream 1.23-stable --follow-tags
• Run the Jenkins Tarballs Release to create tarballs
• Update release version similar to here
• Sign Tarballs
  • Download
  • Inspect
  • Sign and upload detached signatures

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

Background documentation

• Update foreman-packaging
  • rpm/1.23
  • deb/1.23 branches
• Trigger release_packages in Jenkins by calling release_packages script.
• Tag foreman-release into foreman-client-1.23-rhel7, as this doesn’t happen automatically for that one tag: koji tag-build foreman-client-1.23-rhel7 foreman-release-1.23.2-1.el7
• Sign the RPMs in the release
  • Download
  • Sign
  • Upload RPM signatures
  • Upload RPMs
• Sign RPMs for client repos (call scripts with PROJECT=client)
  • Download
  • Sign
  • Upload RPM signatures
  • Upload RPMs
• 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

[ehelms]

All release pipelines completed.