LTS 2.332.3

[NotMyFault]

Next LTS release

Release Lead

@NotMyFault

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.: #228
    - [ ] 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.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

• 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:
  jenkinsci/jenkins#6472
  jenkinsci/packaging#308 - cancelled, because all changes are already included in .2.

• Review ATH, bom and configuration-as-code integration tests results
  🟢 https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/job/PR-6472/

• Prepare LTS changelog based on the style guide using the changelog generator - This is normally done by the docs team, ask in gitter
  🟢 jenkins-infra/jenkins.io#5101

• Prepare LTS upgrade guide based on previous upgrade guides - This is normally done by the docs team, ask in gitter
  🟢 jenkins-infra/jenkins.io#5101

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.3-rc

• Send announcement email, example: https://groups.google.com/g/jenkinsci-dev/c/tSY-OtnkXr0

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

• 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

• 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: jenkinsci/bom#1102

• Create pull request to update configuration-as-code integration tests to the newly released version: jenkinsci/configuration-as-code-plugin#1966

• 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: jenkins-infra/helpdesk#2916

[timja]

Feel free to send a VPN request so you can see the CI instances:
https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access

[NotMyFault]

Feel free to send a VPN request so you can see the CI instances: https://github.com/jenkins-infra/docker-openvpn#howto-get-client-access

Thanks, heading forward to do that later! Would you mind adding me to the release team? I don't think I'm able to publish a pre-release on GitHub otherwise.

[timja]

Done

[NotMyFault]

@timja could you run the docker job on trusted.ci please?

[MarkEWaite]

@timja could you run the docker job on trusted.ci please?

Job ran about 2 hours ago and has published the tags. Thanks!

[NotMyFault]

@timja could you run the docker job on trusted.ci please?

Job ran about 2 hours ago and has published the tags. Thanks!

Thanks for the confirmation, Mark.

Hopefully we can have this job on release.ci soonish 👀

[MarkEWaite]

Hopefully we can have this job on release.ci soonish 👀

jenkins-infra/helpdesk#2845

[NotMyFault]

I'm going ahead and close this issue. The checklist is complete and the release build is available for GA 🎉

[MarkEWaite]

Thanks very much @NotMyFault for being the release lead on Jenkins 2.332.3. Much appreciated!

[timja]

Thanks Alex!