You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. Init 2.387.1 jenkinsci/bom#1753
Update jira labels for lts-candidate issues, either add 2.361.2-fixed and remove lts-candidate or add 2.361.2-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
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.
Security release superseded this step.
Check LTS changelog is visible on the downloads site
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.361).
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.361).
Adjust state and Released As of Jira issues fixed in the release (see the changelog for issue links)
Next LTS release
More information about the release process is available on the release guide.
Release Lead
@NotMyFault
Prep work
LTS baseline discussed and selected in the Jenkins developers mailing list
https://groups.google.com/g/jenkinsci-dev/c/jXk4L0aRs5k/m/JtaXu5klBAAJ
Create or update release branch in jenkinsci/jenkins, e.g.
stable-2.361
, use the init-lts-line scriptCreate or update release branch in jenkins-infra/release, e.g.
stable-2.361
.RELEASE_GIT_BRANCH
andJENKINS_VERSION
values in the environment file (profile.d/stable
) to match the release.PACKAGING_GIT_BRANCH
value in the packaging script (Jenkinsfile.d/core/package
) to match the release.Create or update release branch in jenkinsci/packaging, e.g.
stable-2.361
Init 2.387.1 #323
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.
Init 2.387.1 jenkinsci/bom#1753
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)
Init next LTS line jenkinsci/configuration-as-code-plugin#2206
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
https://groups.google.com/g/jenkinsci-dev/c/m1Uoq7y2Otk
Update jira labels for lts-candidate issues, either add
2.361.2-fixed
and removelts-candidate
or add2.361.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-lts
label and summary of changes in description from lts-candidate-stats script andBackporting for 2.387.1 jenkinsci/jenkins#7650
Review ATH, bom and configuration-as-code integration tests results
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-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.361.1-rc32701.b_06d9cef554c/jenkins-war-2.361.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.Security release superseded this step.
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.361
).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.361
).Adjust state and
Released As
of Jira issues fixed in the release (see the changelog for issue links)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
andrelease.ci
to the new LTS release, exampleThe text was updated successfully, but these errors were encountered: