chore(updatecli): keep default JENKINS_VERSION and WAR_SHA up to date#2171
Merged
lemeurherve merged 8 commits intojenkinsci:masterfrom Jan 11, 2026
Merged
Conversation
lemeurherve
commented
Jan 5, 2026
| kind: shell | ||
| name: Get latest Jenkins Core sha256 checksum | ||
| spec: | ||
| command: curl --disable --fail --silent --show-error --location "https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/{{ source "latestVersion" }}/jenkins-war-{{ source "latestVersion" }}.war.sha256" |
Member
Author
There was a problem hiding this comment.
Suggested change
| command: curl --disable --fail --silent --show-error --location "https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/{{ source "latestVersion" }}/jenkins-war-{{ source "latestVersion" }}.war.sha256" | |
| command: gh release view "jenkins-{{ source "latestVersion" }}" --repo jenkinsci/jenkins --json assets --jq '.assets[] | select(.name == "jenkins.war").digest' | sed 's/sha256://' |
FWIW, I had the command above in my first draft, replaced to use the same as in
Line 85 in 52d8ee8
JENKINS_VERSION up to dateJENKINS_VERSION and WAR_SHA up to date
6 tasks
c4aeb0c to
95a7475
Compare
lemeurherve
commented
Jan 8, 2026
Comment on lines
+72
to
+73
| - tests/golden/expected_tags.txt | ||
| - tests/golden/expected_tags_latest_weekly.txt |
Member
Author
There was a problem hiding this comment.
Note: no update for the LTS golden file, as it now properly uses the simulated LTS JENKINS_VERSION and not the default JENKINS_VERSION.
The update of this LTS golden file is done with #2172
Ref:
timja
approved these changes
Jan 10, 2026
| kind: shell | ||
| name: Get latest Jenkins Core sha256 checksum | ||
| spec: | ||
| command: curl --disable --fail --silent --show-error --location "https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/{{ source "latestVersion" }}/jenkins-war-{{ source "latestVersion" }}.war.sha256" |
Member
There was a problem hiding this comment.
https://updates.jenkins.io/latestCore.txt is the official method of getting the latest core version
Member
Author
|
Not sure why no PR has been opened by updatecli, from last logs on masterhttps://github.com/jenkinsci/docker/actions/runs/20894353415/job/60030463486: |
This was referenced Jan 15, 2026
Merged
6 tasks
This was referenced Jan 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds an updatecli manifest to keep the default
JENKINS_VERSIONandWAR_SHAvalues up to date.Ref:
JENKINS_VERSIONshould be updated more frequently #2165Testing done
updatecli diff --config ./updatecli/updatecli.d/jenkins-version.yaml --values ./updatecli/values.github-action.yaml
Submitter checklist