helpdesk
helpdesk copied to clipboard
jenkins-infra
https://updates.jenkins.io/stable/latest/jenkins.war returns 404
Service(s)
Update center
Summary
Our tests get the latest LTS by querying https://updates.jenkins.io/stable/latest/jenkins.war, it's been returning 404 for several weeks.
Reproduction steps
â ~ curl -L -I https://updates.jenkins.io/stable/latest/jenkins.war
HTTP/2 302
date: Tue, 25 Feb 2025 10:10:54 GMT
content-type: text/html; charset=iso-8859-1
location: https://updates.jenkins.io/dynamic-stable-2.492.1/latest/jenkins.war
strict-transport-security: max-age=2592000; includeSubDomains; preload
HTTP/2 404
date: Tue, 25 Feb 2025 10:10:54 GMT
content-type: text/html; charset=iso-8859-1
vary: Accept-Encoding
strict-transport-security: max-age=2592000; includeSubDomains; preload
Take a look at these similar issues to see if there isn't already a response to your problem:
- 95% #3927
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
As far as I understand it, https://updates.jenkins.io/stable/latest/jenkins.war is not a documented location to obtain the most recent LTS release. We switched the Jenkins update center to use Cloudflare and as part of that change, some of the undocumented locations (like https://updates.jenkins.io/stable/latest/jenkins.war) are no longer providing that data.
You'll need to switch to use a documented location to obtain the most recent Jenkins LTS war file. The downloads page provides a link to the most recent Jenkins war file for LTS and for weekly. The Permalinks to latest files page provides a link to the most recent Jenkins war file for weekly.
The update center documentation says /stable/latestCore.txt is used by the jenkins-infra/jenkins.io build to determine the current LTS release. You can read the contents of that file to determine the version number and then form the download URL with the contents of that file.
As far as I understand it,
https://updates.jenkins.io/stable/latest/jenkins.waris not a documented location to obtain the most recent LTS release. We switched the Jenkins update center to use Cloudflare and as part of that change, some of the undocumented locations (likehttps://updates.jenkins.io/stable/latest/jenkins.war) are no longer providing that data.You'll need to switch to use a documented location to obtain the most recent Jenkins LTS war file. The downloads page provides a link to the most recent Jenkins war file for LTS and for weekly. The Permalinks to latest files page provides a link to the most recent Jenkins war file for weekly.
The update center documentation says
/stable/latestCore.txtis used by the jenkins-infra/jenkins.io build to determine the current LTS release. You can read the contents of that file to determine the version number and then form the download URL with the contents of that file.
yes, but it was fixed last time: https://github.com/jenkins-infra/helpdesk/issues/3927 ...
yes, but it was fixed last time: https://github.com/jenkins-infra/helpdesk/issues/3927 ...
Indeed. Implementing this "alias" on the consumer side seemed more breakage-prone, isn't there a stable alias link to the latest LTS we can use? There is one for the latest release: https://updates.jenkins.io/latest/jenkins.war.
Most places hardcore the version and then have a PR generated by the likes of renovate so you don’t get random broken builds when it updates
Implementing this "alias" on the consumer side seemed more breakage-prone, isn't there a stable alias link to the latest LTS we can use? There is one for the latest release: https://updates.jenkins.io/latest/jenkins.war.
I'm not aware of an alias for the most recent LTS.
I'm also experiencing this issue with a 404 after a redirect from https://updates.jenkins.io/stable/latest/jenkins.war takes me to https://updates.jenkins.io/dynamic-stable-2.492.1/latest/jenkins.war
Most places hardcore the version and then have a PR generated by the likes of renovate so you don’t get random broken builds when it updates
I'm playing around this idea on a branch. Is the Renovate app installed on the jenkcinsci organization?
Most places hardcore the version and then have a PR generated by the likes of renovate so you don’t get random broken builds when it updates
I'm playing around this idea on a branch. Is the Renovate app installed on the jenkcinsci organization?
Yes although not currently on all repositories, I've enabled it on the gradle-plugin one.
This issue is still present - any update / progress here? the URL now redirects to https://updates.jenkins.io/dynamic-stable-2.504.1/latest/jenkins.war which 404's
This issue is still present - any update / progress here? the URL now redirects to https://updates.jenkins.io/dynamic-stable-2.504.1/latest/jenkins.war which 404's
As far as I know, there is no plan to create a redirect from https://updates.jenkins.io/stable/latest/jenkins.war that points to the current LTS.
This issue is still present - any update / progress here? the URL now redirects to https://updates.jenkins.io/dynamic-stable-2.504.1/latest/jenkins.war which 404's
No progress here, as it is really a low priority for the infra team (it has never been a feature, so we cannot put this in front of other major tasks). We do want to add it as a nice feature for users (like you) but we did not have had time on this (hence no status update on the issue).
We keep the issue in the milestone "infra-team-sync-next" which is our "reserve" of issues to look into once the top major things have been covered. It means it will be updated as soon as we'll have time to spend on it.
Most places hardcore the version and then have a PR generated by the likes of renovate so you don’t get random broken builds when it updates
I'm playing around this idea on a branch. Is the Renovate app installed on the jenkcinsci organization?
Yes although not currently on all repositories, I've enabled it on the gradle-plugin one.
FWIW, this renovate conf seems to work fine for us:
https://github.com/jenkinsci/gradle-plugin/blob/master/.github/renovate.json#L16-L51