LTS 2.426.1

[MarkEWaite]

LTS 2.426.1 release checklist

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

Release Lead

@MarkEWaite

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.387, use the init-lts-line script or carry out the equivalent steps therein.

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

  • 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.

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

• 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.

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

  • Eligible
    • Fix vSphere cloud agent label assignment - JENKINS-71937
    • Fix HTTP/2 rapid reset by upgrading to Jetty 10.0.17 JENKINS-72156
    • Display form validation for initially hidden fields - JENKINS-71252
    • Form validation does not clear previous errors - JENKINS-70793
    • Cannot add additional branch sources in multibranch - JENKINS-72170
    • Remoting retry - JENKINS-72163
    • Show checkbox parameter descriptions in build view - JENKINS-72179
    • Add telemetry for Jenkins uptime - PR-8596
    • Allow clouds to be reordered - JENKINS-72020
    • Fix drag & drop for repeatables - JENKINS-72189 & JENKINS-71089

• Extend the update center security warning exclusion to not warn for 2.426.1 with a pull request

• 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.

• Update Jira labels for lts-candidate issues, either add 2.426.1-fixed and remove lts-candidate or add 2.426.1-rejected, and retain lts-candidate.

• 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.

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

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

• Open an acceptance test harness pull request and a plugin bill of materials pull request to confirm the incremental produced by the backporting PR doesn't contain regressions.
  The documentation explains which profiles you have to modify in your PR.

• Submit pull request to update the dependabot branch target in jenkinsci/jenkins to the new stable branch (strike this out for new point release).

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

• Prepare LTS upgrade guide pull request 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 (and do not squash). Visible at https://github.com/jenkinsci/jenkins/tree/stable-2.426

  • Merge second backporting PR using a merge commit and follow later steps to generate new release candidate

• Retrieve the URL for the RC

  • Retrieve the URL for the second RC

• Publish a pre-release Github release,

  • Publish a second pre-release GitHub release

• Confirm the automatic announcement has been sent to the jenkinsci-dev mailing list and community forums.

  • Confirm the second announcement

• 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).

• Announce the start of the LTS release process in the #jenkins-release:matrix.org channel.

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

• Check LTS changelog is visible on the downloads site.

• Publish GitHub release pointing to LTS changelog, sample.

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

• 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).

• Confirm that the war download link with ?mirrorlist appended shows multiple mirrors are delivering the release https://get.jenkins.io/war-stable/2.426.1/jenkins.war?mirrorlist

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

• Create pull request to update the lts Maven profile in ATH to the newly released version

  • Use 2.426.1 in lts profile instead of 2.414.3 jenkinsci/acceptance-test-harness#1417

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

• Confirm that the images are available at Docker hub.

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

  • chore(deps): bump lts to 2.426.1 jenkinsci/helm-charts#945

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

  • Update ci.jenkins.io, trusted.ci, cert.ci and release.ci to latest LTS version 2.426.1 helpdesk#3820

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

[MarkEWaite]

Release is complete including all items on the checklist.