The Jenkins project provides a download mirror infrastructure allowing to download Jenkins packages and plugins from a download server close to your location.

How Does it Work?

When a download request is emitted to eithermirrors.jenkins.ioorget.jenkins.io, an HTTP redirect response to a mirror download server is answered.

The Jenkins infrastructure uses a database of existing mirror servers provided by volunteers and donators to select the closest mirror to your location: this is currently the role of the distinctmirrors.jenkins.ioandget.jenkins.ioservices.

Consolidation

The system behindmirrors.jenkins.iois using a software named"mirrorbrain"and was originally used by the Jenkins infrastructure to provide download redirections to mirrors.

A new system was introduced in 2020:get.jenkins.io, using"mirrorbits"which is a great fit for a Kubernetes environment (lightweight, horizontally scalable) and provides a set of nice WebUI features to see the mirror list and grading.

INFO: Try it by yourself, check the mirrors providing the latest Jenkins LTS distribution:https://get.jenkins.io/war-stable/2.332.3/jenkins.war?mirrorlist

It’s been 2 years and the new system is clearly the most reliable: that’s why we, the Jenkins Infrastructure team, want to retire the "mirrorbrain" system.

In consequence, the 19th of May 2022, the domain namemirrors.jenkins.iowill be changed to point to the actual "mirrorbits" system already available atget.jenkins.io.

This consolidation ensures all users downloading a Jenkins package or a plugin will use the closest download mirror to their location, without having to maintain 2 distinct systems.

Enforced HTTPS

The main consequence is that the HTTPS protocol will be enforced for the request to the domainmirrors.jenkins.io.

The "mirrorbrain" system currently serving requests behind the domainmirrors.jenkins.iois not available through HTTPS, which is a safety issue for users downloading files.

The 19th of May 2022, that won’t be the case anymore: likeget.jenkins.io, HTTPS will be available and enforced for the requests going through the domainmirrors.jenkins.io.

What Does It Change for Me?

  • Short answer: nothing. You should already be using the domainget.jenkins.ioas it’s been the default since almost 2 years, and the content served by both system is the same.

  • Long answer: if you are still using the formermirrors.jenkins.ioand are not able to switch toget.jenkins.io, you’ll see the following changes:

  • The mirror usually selected might change as the grading system on mirrorbits is different (and covers way more mirrors): faster downloads for you!

  • Your HTTP requests will be redirected to their corresponding URL using the HTTPS protocol with a valid TLS certificate signed by the Let’s Encrypt authority: improved safety!

  • ⚠️ The IP pointed by the DNS recordmirrors.jenkins.iowill change from52.202.51.185to52.167.253.43: upgrade your proxies!

About the Authors
Damien DUPORTAL

Damien is theJenkins Infrastructure officerand a software engineer atCloudBeesworking as a Site Reliability Engineer for theJenkins Infrastructure project. Not only he is a decade-old Hudson/Jenkins user but also an open-source citizen who participates inUpdatecli,Asciidoctor,Traefikand many others.