-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not rely on the tiered update center directory layout #954
Comments
Here's the proposed change that will impact |
Can we make 2.235 the last update center tier to support? I.e. 2.24x would no longer be a fixed tier? @slide ? |
I would love to make that possible, I haven't had a chance to look into this yet though. I will try and look into it today if I can manage some time. |
See #964 964 |
@daniel-beck do you know if this issue is still relevant? |
Not since #1408 |
For the record, I asked that as I found this issue linked in https://github.com/jenkins-infra/update-center2/blob/77bcef2630467ba31f4bcabdec74421f2ca629e3/site/README.md#L38-L39 while working on jenkins-infra/helpdesk#2649 |
The canonical way to access a version-compatible update site is through
/update-center.json?version=...
.Do not rely on
/stable-2.222/update-center.json
,/2.222/update-center.json
, etc. to exist. Those are implementation details that may change at any time.The text was updated successfully, but these errors were encountered: