LTS 2.387.2 #345
Labels
lts-checklist
This issue tracks the progress of an LTS release
Comments
krisstern
added
the
lts-checklist
|
I wanted to share the changelog & upgrade guide PR as I have just created them jenkins-infra/jenkins.io#6173 I made sure to only include the three that made it into this LTS, so the New Node ticket will be added next time. |
MarkEWaite
added a commit
to jenkins-infra/jenkins.io
that referenced
this issue
Mar 31, 2023
This pull request is to add the changelog to jenkins-infra/release#345, as the backports are available and the intention is to release the LTS tomorrow (2023-03-22). The upgrade guide has been added as well, but there are no entries for it so it has been left as others. --------- Co-authored-by: Mark Waite <mark.earl.waite@gmail.com> Co-authored-by: Alexander Brandes <brandes.alexander@web.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
LTS 2.387.2 release
More information about the release process is available on the release guide.
Release Lead
@krisstern
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.Create or update release branch in jenkins-infra/release, e.g.
stable-2.387.RELEASE_GIT_BRANCHandJENKINS_VERSIONvalues in the environment file (profile.d/stable) to match the release.PACKAGING_GIT_BRANCHvalue in the packaging script (Jenkinsfile.d/core/package) to match the release.Init LTS 2.387.2 #347
Create or update release branch in jenkinsci/packaging, e.g.
stable-2.387.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).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.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-candidatelabel, 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.387.2-fixedand removelts-candidateor add2.387.2-rejected, and retainlts-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-ltslabel and summary of changes in description from lts-candidate-stats script and:Backporting for LTS 2.387.2 jenkinsci/jenkins#7759
Review ATH, bom and configuration-as-code integration tests results.
🟢 ATH: https://ci.jenkins.io/job/Core/job/acceptance-test-harness/
🟢 BOM: https://ci.jenkins.io/job/Tools/job/bom/
🟢 Configuration-as-code: https://github.com/jenkinsci/configuration-as-code-plugin/actions/runs/4485070487
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-warURL 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 incrementals are broken you can deploy a build from your own machine withmvn -e clean deploy -DskipTests=true.Publish a pre-release Github release, e.g. sample currently we don't have a changelog for RCs.
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).
Announce the start of the LTS release process in the #jenkins-release and #jenkins-infra IRC channels.
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).Adjust state and
Released Asof Jira issues fixed in the release (see the changelog for issue links).2.387.2-fixedissues as "Closed" and "Fixed".Run trusted.ci.jenkins.io Docker image creation job.
Confirm that the images are available at Docker hub.
https://hub.docker.com/r/jenkins/jenkins/tags?page=1&name=2.387.2
Create a helpdesk ticket to update
ci.jenkins.io,trusted.ci,cert.ciandrelease.cito the new LTS release, example.Update ci.jenkins.io, trusted.ci, cert.ci and release.ci to latest LTS version 2.387.2 helpdesk#3490
The text was updated successfully, but these errors were encountered: