dduportal
commented
2 hours ago Update:
- Initial PR on the update center2 generation: https://github.com/jenkins-infra/update-center2/pull/816
- This PR was deployed successfully
- The directory listing are back:
- https://azure.updates.jenkins.io/current/
- While directory with an
index.htmlare served by Apache like it was before: - https://azure.updates.jenkins.io
- https://azure.updates.jenkins.io/current/latest
- And the usual JSON files are served by the mirrors:
- https://azure.updates.jenkins.io/update-center.json -> https://mirrors.updates.jenkins.io/update-center.json -> mirrors
- https://azure.updates.jenkins.io/dynamic-2.476/update-center.json -> https://mirrors.updates.jenkins.io/dynamic-2.476/update-center.json
- Jenkins Controllers are still working well with the current azure.updates.jenkins.io
- 🔴 The "JSON wrapped in HTML" files are not redirected to mirrors (example: https://azure.updates.jenkins.io/current/update-center.json.html)
- 🔴 The tools
/updatespath is not providing a directory listing: https://azure.updates.jenkins.io/updates/ - 🟡 We don't have a favicon: https://azure.updates.jenkins.io/favicon.ico (HTTP/404)
Next steps:
- We have to cover the whole
/updatespath along with the crawler to:- Provide all files to Apache (it's only published to mirrors right now) to have a listing directoris at https://azure.updates.jenkins.io/
- We need to fix the
.json.htmlwrapped files to be served by mirrors - Favicon ? ;)
ref. https://github.com/jenkins-infra/helpdesk/issues/2649#issuecomment-2443912336
This issue tracks the work related to moving back workloads from mirrors to front Apache to allow directory listing.
As described in the linked comment, we want to have ALL files available in Apache (e.g. azure.updates.jenkins.io), and we'll only redirect requests to mirrors(.updates.jenkins.io) on heavily downloaded files.