Thanks Olivier for the feedback!
Le vendredi 6 mai 2022 à 08:48:19 UTC+2, Olblak a écrit :
Is there any motivation to not just redirect traffic from mirror.jenkins.io
> to get.jenkins.io
> that would only be one CNAME change.
>
That is the idea as a "fallback", even though it requires an
Hey,
> One of the first steps is to change the code on the Jenkins project that uses
> the old "mirror.jenkins.io" and change it to https://get.jenkins.io.
Is there any motivation to not just redirect traffic from mirror.jenkins.io to
get.jenkins.io
that would only be one CNAME change.
And if
Hello dear contributors!
The infrastructure team is going, in the upcoming weeks, to sunset the
service "mirror.jenkins.io" in favor of get.jenkins.io.
More details can be found in this issue:
https://github.com/jenkins-infra/helpdesk/issues/2888.
One of the first steps is to change the code
