[INFRA-2435] Switch back from repo.azure.jenkins.io to repo.jenkins-ci.org #2047
Comments
|
It requires some work to migrate it to the new location and considering that service is not faster than repo.jenkins-ci.org, we will just let it die with prodbean. I am switching every occurrence of repo.azure.jenkins.io to repo.jenkins-ci.org |
|
Pull request opens on jenkins-infra/pipeline-library#/135 |
|
> repo.jenkins-ci.org doesn't seem to be less stable or slower than azure.repo.jenkins.io so let remove it.
Would it be possible to provide some metrics about it? I have a different experience with my jobs?
|
|
Also, what will be the outbound/inbound traffic cost if we get rid of the internal mirror? |
|
To test the speed, I run curl on "big" files from ci.jenkins.io (master) as you can see on this screenshot |
|
Thanks! One-time download does not make much difference, because it does not emulate a real use-case. I would recommend running a clean build of a heavy component like JCasC plugin or Blue Ocean and to see the speed there. Maven does parallel downloads of hundreds of artifacts, and the result might be different. Also waiting for the info about traffic costs
|
|
The best and easy way to test this, is just by merging my PR and see who ci.jenkins.io behaves Regarding the cost analysis, it's hard to tell I don't have anything in place that could easily tell me the bandwidth used for that service |
|
Should developers be deleting the other outstanding references? |
What about stability? From a developer PoV of course build speed is relevant but avoiding flaky build failures is perhaps even more important. Do we have any data about the frequency of download failures from Artifactory vs. the (nginx?) proxy, or is this anecdotal? |
|
Should developers be deleting the other outstanding references? For now yes, I sent an email to move the discussion on the mailing here What about stability? From a developer PoV of course build speed is relevant but avoiding flaky build failures is perhaps even more important. This is a valid concern and we could definitely bring back somehow this service if there is a need for it. I am clausing this ticket for now but we may re-open it if necessary. |
repo.jenkins-ci.org doesn't seem to be less stable or slower than azure.repo.jenkins.io so let remove it.
More information about why we deployed that service, on INFRA-1176
Originally reported by olblak, imported from: Switch back from repo.azure.jenkins.io to repo.jenkins-ci.org
The text was updated successfully, but these errors were encountered: