Artifact caching proxy activation

[Herve Le Meur]

Hello dear contributors,

As explained in this "Artifact caching proxy activation" helpdesk issue, we're planning to activate the artifact caching proxy for all plugins.

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.

I'm writing this mail to check if it's OK for everyone, and 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'll need for whatever reason to disable this mechanism (discouraged), you will have two possibilities:

• on your pull request, add a skip-artifact-caching-proxy label
• in your Jenkinsfile, add useArtifactCachingProxy: false to the recommanded buildPlugin configuration, ex:

buildPlugin(
  useContainerAgent: true,
  useArtifactCachingProxy: false, // Add this line to opt-out of this functionality and bypass the artifact caching proxy
  configurations: [
    [platform: 'linux', jdk: 17],
    [platform: 'windows', jdk: 11],
])

If you've got any questions or issues, please add them to the helpdesk issue.

Kind regards,

Hervé for the Jenkins Infrastructure team

[Mark Waite]

I'm using the artifact caching proxy with 10+ plugins that I maintain without any issue.  +1 from me to make it the standard way.

[Herve Le Meur]

Hello,

As there haven't been any objection, I'm activating the artifact caching proxy for every plugin.

Regards,

Hervé

[Ullrich Hafner]

Does this affect local builds as well? 

I now get failures while trying to fetch incremental releases:

[ERROR] Failed to execute goal on project warnings-ng: Could not resolve dependencies for project io.jenkins.plugins:warnings-ng:hpi:10.0.0-SNAPSHOT: The following artifacts could not be resolved: io.jenkins.plugins:analysis-model-api:jar:11.0.0-rc645.3b_6973434c0b, io.jenkins.plugins:plugin-util-api:jar:3.0.0-rc676.39c5d554b_82f, io.jenkins.plugins:prism-api:jar:1.29.0-3-rc205.6b_6980cca_b_76, io.jenkins.plugins:forensics-api:jar:2.0.0-rc1380.c93c627cd828, io.jenkins.plugins:forensics-api:jar:tests:2.0.0-rc1380.c93c627cd828, edu.hm.hafner:analysis-model:jar:tests:11.0.0-rc4947.d37dc2873c20, io.jenkins.plugins:plugin-util-api:jar:tests:3.0.0-rc676.39c5d554b_82f: Could not find artifact io.jenkins.plugins:analysis-model-api:jar:11.0.0-rc645.3b_6973434c0b in repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/) -> [Help 1]

[

--
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/CAL-Lwjw1_BV2y4VuoN%2Bon5G5dVABzkUi20h%3Do2%2BOE59oWYPcnA%40mail.gmail.com.

[Ullrich Hafner]

Sorry, false alarm :-) Now everything is back to normal...

[Herve Le Meur]

Hello Ullrich,

Good to know :)

Hervé

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ADD45AF0-8924-41C7-A516-993ECC8712EF%40gmail.com.