Says it should be c620cca3c55f1a0441ca04ff7f41696d7057a185ebb63d6d09c182421c8cba8e but is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Potentially corrupted release artifact - should be rolled back immediately
To validate download https://updates.jenkins.io/download/war/2.498/jenkins.war
sha256sum jenkins.war e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Causing war file to seem corrupted
1 Like
I can’t duplicate the problem that you’re reporting. You’ll need to provide more details so that others can duplicate it.
The mirrorlist for Jenkins latest weekly and the mirrorlist for Jenkins 2.498 both show the correct SHA-256 checksum. The file that I download from my nearest mirror provider shows the correct value:
It is a little surprising the SHA-256 checksum that you share in your message e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 is the same checksum referenced in a 2021 issue report to the Jenkins docker container repository. I don’t have any reason why that same checksum would appear in a 2021 issue report about git LFS and in your download.
1 Like
Yep - apologies
Believe I jumped to conclusions here and the issue is somewhere on my end
@MarkEWaite figured it out - https://updates.jenkins.io/stable/latest/jenkins.war
Is pointing to https://updates.jenkins.io/dynamic-stable-2.492.1/latest/jenkins.war
Which is invalid now
converting to useing Index of /download
Path corrected the issue
What suggested that you should use that URL to download a Jenkins release? I’m not aware of any location that suggests that /stable/latest/ is a valid location for Jenkins downloads. If there is such a location, we want to correct it.
The Jenkins download page includes the link https://get.jenkins.io/war-stable/2.492.1/jenkins.war for the LTS version and it includes the link https://get.jenkins.io/war/2.498/jenkins.war for the weekly version.
1 Like
This points you to it
I found it taking over the jenkinsapi python package
@MarkEWaite whats interesting is this worked until around yesterday
I don’t see a reference to /stable/latest/ anywhere in any of the references that you provided. Can you provide a more precise reference?
All usages appear resolved - old file url is working again
I almost can’t believe nothing changed on your side
It’s not.
echo -n '' | sha256sum
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 -
1 Like