Sunsetting mirror.jenkins.io in favor of get.jenkins.io

[Damien Duportal]

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 on the Jenkins project that uses the old "mirror.jenkins.io" and change it to https://get.jenkins.io.

However this might have some impact and the infra team need help to review, challenge and approve this change.

A first step is on the shared pipeline library: https://github.com/jenkins-infra/pipeline-library/pull/374 .

This change request might have an impact on the Jenkins Core build and the test harnesses so better notifying contributors.

ETA of this 1st change is 9th of May unless there is strong reason to not to.

Many thanks in advance!

For the infra team, Damien DUPORTAL

[Olblak]

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 you want to take extra care, we could just announce on the blogpost that HTTP support will be remove in one month.

Anyway the updatecenter only use HTTPS if I recall correctly.

--

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4de12a3f-160d-4b17-baeb-358e718fe884n%40googlegroups.com.

[Damien Duportal]

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 ingress rule to be added to mirrorbits (current service has an ingress for get.jenkins.io) in the Kubernetes cluster.

But changing the domain name helps to track the "HTTP" usages: better to use the actual domain to make it clear in our code. The effort is low and it is a good opportunity to cleanup stuff.

 

And if you want to take extra care, we could just announce on the blogpost that HTTP support will be remove in one month.

We are aligned: that is the TL;DR; of the blog post  \o/