LTS 2.277.2

[timja]

LTS 2.277.2

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

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

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

• 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

  • JENKINS-64972 - help buttons disabled when at top of draggable div. Fixed in PR-5316, included in Jenkins 2.283, no reported regressions
  • JENKINS-64931 - Deadlock with FutureImpl and Queue. Fixed in PR-5305, included in Jenkins 2.283, no reported regressions
  • JENKINS-65186 - Reduce logging of renamed API endpoint. Fixed in PR-5207, included in Jenkins 2.278 without a visible changelog entry, no reported regressions
  • JENKINS-62006 - Fix ClassNotFoundException on agents. Fixed in PR-5367, released in Jenkins 2.285, no reported regressions
  • skipped: PR-5360 Use xstream 1.4.16 - upstream change not expected to impact Jenkins core
  • skipped: PR-5350 and PR-5334 Japanese translations
  • skipped: PR-5341 - Accept negative numbers in INPUT.number - no visible malfunction in browser
  • skipped: PR-5333 - Prevent form validation bugs from damaging page rendering - not flagged as lts-candidate by Daniel Beck (included in 2.283)
  • skipped: PR-5300 - Bump spring-security-bom from 5.4.4 to 5.4.5 - a dependency revert, not expected to impact Jenkins use cases
  • skipped: PR-5298 - Revert "Clean up VirtualFile..." - original PR is not in 2.277.1

• Backporting announcement email - script

• Update jira labels with the selected issues, e.g. 2.263.2-fixed, 2.263.2-rejected

• Backport changes, create a local branch in jenkinsci/jenkins, run the 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 script

• Review ATH, bom and configuration-as-code integration tests results

• Prepare LTS changelog based on the style guide using the changelog generator

• Prepare LTS upgrade guide based on previous upgrade guides

RC creation

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

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

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

• Run job on release.ci.jenkins.io

• Publish a pre-release Github release, currently we don't have a changelog for RCs

• Send announcement email

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

• Run job on release.ci.jenkins.io (packaging job ran on release.ci, build job ran in CERT). Issues with websocket timeout for the Kubernetes agents changed to use websocket, but one successful run.

• 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

• Confirm the Red Hat installer acceptance test is passing

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

• Create pull request to update bom to the newly released version

• Create pull request to update configuration-as-code integration tests to the newly released version

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

• Update ci.jenkins.io to the new LTS release (note: repo is private, requires infra team membership)

[MarkEWaite]

Completed all items. Needs an additional item in the checklist

[ ] Remove the lts-candidate label from Jira issues resolved in the release

Submitted as #146