Artifact caching proxy activation in buildPlugin()
shared pipeline function
#3369
Labels
Milestone
buildPlugin()
shared pipeline function
#3369
The artifact caching proxy is a mechanism we've put in place using nginx proxy in front of repo.jenkins-ci.org (our JFrog sponsored Artifactory instance) and Maven Central to cache artifacts download requests.
The main goals are to decrease the consumed bandwidth (many terabytes per month) and to increase Jenkins infrastructure reliability and resilience.
While this functionality was proposed as opt-in with an handful of plugins participating in the testing, we're planning to activate the artifact caching proxy for all plugins.
I've started a thread on the jenkinsci-dev mailing list to check if it's OK for everyone.
If there is no major objection after a delay of 24 hours, we'll merge this PR around 14:00 UTC on Thursday February 2 to switch this feature as opt-out for all plugins using the
buildPlugin
function from the shared pipeline library.As the caches of these ACPs are warming up, the first plugin builds might take a little bit more time, but the following ones should be quicker.
In case you need for whatever reason to disable this mechanism (discouraged), you have two possibilities:
skip-artifact-caching-proxy
labeluseArtifactCachingProxy: false
to the recommandedbuildPlugin
configuration, ex:If you've got any questions or issues, please add them to this issue.
The text was updated successfully, but these errors were encountered: