-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Remove dependency on latest/ directory #953
Comments
Can you give some details on what the structure will look like? |
@slide It's unclear what you're asking. These directories will no longer be generated. See e.g. https://issues.jenkins-ci.org/browse/INFRA-2615 for a change I plan to implement that will make the existence of update site tiers dependent on what plugins actually declare. Instead, request |
Ok, that makes more sense. |
One thing I noticed is that if you provide a bogus Jenkins version, e.g., |
@slide In that particular case, we provide the We redirect all 1.x versions to the latest, but it really doesn't make that much of a difference anymore, upgrading core is the only thing that matters. Are you seeing other redirects that don't make sense? |
@daniel-beck as the |
@lemeurherve Probably, do you know whether |
as far as I know it doesn't need them |
The update center will stop providing tiered
latest/
directories soon.Please adapt
install-plugins.sh
to work without that.I had switched to the new version of the update site generator yesterday, and these issues were filed:
https://issues.jenkins-ci.org/browse/INFRA-2614
#952 (comment)
The text was updated successfully, but these errors were encountered: