LTS 2.332.2

[imonteroperez]

2.332.2 LTS release

Release Lead

@imonteroperez

Prep work

• LTS baseline discussed and selected in the Jenkins developers mailing list

• Create or update release branch in jenkinsci/jenkins, e.g. stable-2.277, use the init-lts-line script

• Create or update release branch in jenkins-infra/release, e.g. stable-2.277.

  • Modify the RELEASE_GIT_BRANCH and JENKINS_VERSION values in the environment file (profile.d/stable) to match the release.
  • Modify the PACKAGING_GIT_BRANCH value in the packaging script (Jenkinsfile.d/core/package) to match the release.
  • For more info, refer to stable. --> Created Prepare for version 2.332.2 #226

• Create or update release branch in jenkinsci/packaging, e.g. stable-2.277

• Create pull request to update bom to the weekly version that will be the base of the release line (strike this out for new point release)

• Create pull request to update configuration-as-code integration tests to the weekly version that will be the base of the release line (strike this out for new point release)

• Review Jira and GitHub pull requests for additional LTS candidates, adding the 'lts-candidate' label, and ensure that all tickets are resolved in jira --> Reviewed in Jira. No PRs on GH as LTS candidates.

• Backporting announcement email - generate-backporting-announcement script

• Update jira labels for lts-candidate issues, either add 2.277.2-fixed and remove lts-candidate or add 2.277.2-rejected, and retain lts-candidate

• Backport changes, create a local branch in jenkinsci/jenkins, run the list-issue-commits script to locate commits via jira ID, some manual work is required to locate them if the issue ID wasn't present at merge time, backport with git cherry-pick -x $commit

• Open backporting PR with into-lts label and summary of changes in description from lts-candidate-stats script and the selected Jira lts-candidates --> Backport PR: Backporting for LTS 2.332.2 jenkinsci/jenkins#6401 and also required Backporting for LTS 2.332.2 jenkinsci/packaging#299 for backporting packaging related code. Additional backport due to a missed commit in the previous one: Additional backporting for LTS 2.332.2 jenkinsci/jenkins#6425. Additional backport on packaging: Include war location fix and remove limits.conf reference jenkinsci/packaging#304

• Review ATH, bom and configuration-as-code integration tests results - Waiting for results on: https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-6401/1/pipeline --> Everything looks good 🟢 --> https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-6425/1/pipeline/30 reviewed for second backports and everything looking good 🟢

• Prepare LTS changelog based on the style guide using the changelog generator - This is normally done by the docs team, ask in gitter

• Prepare LTS upgrade guide based on previous upgrade guides - This is normally done by the docs team, ask in gitter

RC creation

• Merge backporting PR in jenkinci/jenkins using a merge commit (do not squash)

• Retrieve the url for the RC from the commit status (Jenkins Incrementals Publisher / Incrementals) of the last build on the stable branch (requires a passing build). Visit the jenkins-war URL and copy the URL of the war file, which would be something like https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.303.2-rc31385.6eec6c02fc3d/jenkins-war-2.303.2-rc31385.6eec6c02fc3d.war. If incrementals are broken you can deploy a build from your own machine with mvn -e clean deploy -DskipTests=true.

• Publish a pre-release Github release, e.g. sample currently we don't have a changelog for RCs --> https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.332.2-rc

• Send announcement email, example

• Check with security team that no security update is planned. If a security update is planned, revise the checklist after the public pre-announcement to the jenkinsci-advisories mailing list

LTS release

• Publish changelog (one day prior to the release in case of a security update) --> 2.332.2 changelog and upgrade guide jenkins.io#5045

• Assure that contents of master branch have been merged to the stable branch in the release repository, e.g. stable-2.277

• Assure that contents of master branch have been merged to the stable branch in the packaging repository, e.g. stable-2.277 --> [JENKINS-68170] Show warning dialog if Java 8 is selected (#302) jenkinsci/packaging#306

• Run job on release.ci.jenkins.io

• Check LTS changelog is visible on the downloads site

• Publish GitHub release pointing to LTS changelog

• Confirm Datadog checks are passing

• Confirm the Debian installer acceptance test is passing.
  For good measures, check the console log to confirm that the correct release package was used (e.g. search for 2.277).

• Confirm the Red Hat installer acceptance test is passing.
  For good measures, check the console log to confirm that the correct release package was used (e.g. search for 2.277).

• Adjust state and Released As of Jira issues fixed in the release (see the changelog for issue links)

• Create pull request to update bom to the newly released version --> Test against new LTS 2.332.2 jenkinsci/bom#988

• Create pull request to update configuration-as-code integration tests to the newly released version --> Bump jenkins.version to 2.332.2 jenkinsci/configuration-as-code-plugin#1944

• Run trusted.ci.jenkins.io Docker image creation job.

• Confirm that the images are available at Docker hub

• Create a helpdesk ticket to update ci.jenkins.io, trusted.ci, cert.ci and release.ci to the new LTS release, example

[imonteroperez]

@timja not sure if this jenkinsci/packaging#306 should be merged or not. Merging things from master to LTS branch sounds weird to me. Do you mind to confirm? Thanks in advance!

[timja]

That looks fine to merge go for it

[imonteroperez]

@timja additional request here, not able to reach https://release.ci.jenkins.io/blue/organizations/jenkins/core%2Fstable%2Frelease/branches/ :-( - I guess it is behind a Jenkins project VPN right? - do you mind taking a look and launching it?

[timja]

Sure, feel free to get VPN access setup: https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access

[timja]

Triggered https://release.ci.jenkins.io/job/core/job/stable/job/release/job/stable-2.332/2/

[imonteroperez]

Sure, feel free to get VPN access setup: https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access

• [infra-admin] Submit certificate request for imontero docker-openvpn#152
• Request access to Jenkins project VPN helpdesk#2867

[imonteroperez]

jenkins-infra/helpdesk#2869

[imonteroperez]

Release is done \o/