Service(s)

infra.ci.jenkins.io

Summary

https://github.com/jenkins-infra/jenkins.io/blob/9addc32ac8d366e02a9ec49e07e81ab527547cf4/scripts/fetch-external-resources#L36
and
https://github.com/jenkins-infra/jenkins.io/blob/9addc32ac8d366e02a9ec49e07e81ab527547cf4/scripts/fetch-external-resources#L66

cause site publishing to be reliant on ci.jenkins.io being up.

Which makes ci.jenkins.io a critical path for publishing security advisories and for contributors developing local site builds.

We should decouple these by publishing to some kind of storage.
Either reports.jenkins.io or an Azure storage, these need to be published publicly somewhere that any contributors machine can download from

see also #3086 (comment)

Reproduction steps

No response