LTS 2.401.3

[krisstern]

LTS 2.401.3 release

More information about the release process is available on the release guide.

Release Lead

@krisstern

Prep work

• [x] LTS baseline discussed and selected in the Jenkins developers mailing list.

• [x] Create or update release branch in jenkinsci/jenkins, e.g. stable-2.387, use the init-lts-line script or carry out the equivalent steps therein.

• [x] Create or update release branch in jenkins-infra/release, e.g. stable-2.387.

  • [x] Modify the RELEASE_GIT_BRANCH and JENKINS_VERSION values in the environment file (profile.d/stable) to match the release.
  • [x] Modify the PACKAGING_GIT_BRANCH value in the packaging script (Jenkinsfile.d/core/package) to match the release.
  • For more info, refer to stable. https://github.com/jenkins-infra/release/pull/396

• [x] Create or update release branch in jenkinsci/packaging, e.g. stable-2.387.

• [x] ~~Create a pull request to update bom to the weekly version that will be the base of the release line (and strike this out for new point release). Assure that the bom-weekly version number is already testing the base of the release line or a version newer than the base of the release line.~~

• [x] Review Jira and GitHub pull requests for additional LTS candidates, adding the lts-candidate label, and ensure that all tickets are resolved in Jira.

• [x] Send a backporting announcement email to the jenkinsci-dev mailing list, using the default template. Remember to exchange the LTS version, release date and Jira URLs.

• [x] Update Jira labels for lts-candidate issues, either add 2.387.2-fixed and remove lts-candidate or add 2.387.2-rejected, and retain lts-candidate.

• [x] Backport changes, 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. https://github.com/jenkinsci/jenkins/pull/8247

• [x] Open backporting PR with into-lts label and summary of changes in description from lts-candidate-stats script and:

  • [x] the selected Jira lts-candidates.
  • [x] possible LTS candidates in the release repository.
  • [x] possible LTS candidates in the packaging repository.

• [x] Review ATH and bom integration tests results. 🟢 https://ci.jenkins.io/job/Core/job/acceptance-test-harness/ 🟢 https://ci.jenkins.io/job/Tools/job/bom/

• [x] Update the dependabot branch target in jenkinsci/jenkins to the new stable branch.

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

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

RC creation

• [x] Merge backporting PR in jenkinci/jenkins using a merge commit (and do not squash).

• [x] 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.387.1-rc32701.b_06d9cef554c/jenkins-war-2.387.1-rc32701.b_06d9cef554c.war. If the incrementals are broken you can deploy a build from your own machine with mvn -e clean deploy -DskipTests=true.

  • https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.401.3-rc33578.5f3947a_c72fc/jenkins-war-2.401.3-rc33578.5f3947a_c72fc.war

• [x] Publish a pre-release Github release, e.g. sample currently we don't have a changelog for RCs.

• [x] Send announcement email, example.

• [x] 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.

  • Yes, security update is planned.

LTS release

• [x] Publish changelog (one day prior to the release in case of a security update).

• [x] Announce the start of the LTS release process in the #jenkins-release and #jenkins-infra IRC channels

• [x] Run job on release.ci.jenkins.io if no security release for Jenkins is planned.

• [x] Check LTS changelog is visible on the downloads site.

• [x] Publish GitHub release pointing to LTS changelog, sample.

• [x] Confirm Datadog checks are passing.

• [x] 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.387).

• [x] 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.387).

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

• [x] Create pull request to update the lts Maven profile in ATH to the newly released version https://github.com/jenkinsci/acceptance-test-harness/pull/1294

• [x] Create a tag matching the LTS release you create in the docker repository and publish a GitHub release.

• [x] Confirm that the images are available at Docker hub.

• [x] Merge the PR generated by the jenkins-dependency-updater bot in the jenkinsci/helm-charts repository.

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

• [x] Send email asking for the next release lead, example, dates for the next one can be found on the Jenkins calendar.

[kmartens27]

Adding the changelog & upgrade guide PR here https://github.com/jenkins-infra/jenkins.io/pull/6533

[krisstern]

Thanks @kmartens27!