Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Artifact caching proxy activation in buildPlugin() shared pipeline function #3369

Closed
lemeurherve opened this issue Feb 1, 2023 · 6 comments

Comments

@lemeurherve
Copy link
Member

lemeurherve commented Feb 1, 2023

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:

buildPlugin(
  useContainerAgent: true, // Set to `false` if you need to use Docker for containerized tests
  useArtifactCachingProxy: false,
  configurations: [
    [platform: 'linux', jdk: 17],
    [platform: 'windows', jdk: 11],
])

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

@kmartens27

This comment was marked as resolved.

@kmartens27

This comment was marked as resolved.

@lemeurherve lemeurherve self-assigned this Feb 1, 2023
@lemeurherve lemeurherve added this to the infra-team-sync-2023-02-07 milestone Feb 1, 2023
@smerle33 smerle33 unpinned this issue Feb 2, 2023
@smerle33 smerle33 pinned this issue Feb 2, 2023
@lemeurherve
Copy link
Member Author

As there were no objection, the PR has been merged, the artifact caching proxy is enabled for every plugin.

@jglick
Copy link

jglick commented Feb 2, 2023

BTW are there separate tasks to enable it for jenkins, bom, etc.?

@dduportal
Copy link
Contributor

BTW are there separate tasks to enable it for jenkins, bom, etc.?

Not yet, we are drafting the plan for it. Most probably we'll continue with the bom.

@lemeurherve lemeurherve changed the title 📣 Artifact caching proxy activation Artifact caching proxy activation in buildPlugin() shared pipeline function Feb 7, 2023
@lemeurherve
Copy link
Member Author

Working as expected, closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment