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

[ci.jenkins.io] Use the jenkins-infra's Artifact Caching Proxy to benefit from cached artifacts #541

Open
dduportal opened this issue Sep 21, 2023 · 3 comments

Comments

@dduportal
Copy link
Contributor

With #537, the build stability was restored by opting-out of the "ACP" (Artifact Caching Proxy) system on ci.jenkins.io.

The (integration) tests failures are rooted into the resulting settings.xml passed to inner Maven invokation on each IT: on ci.jenkins.io, this src/it/settings.xml file is merged with the infrastructure's custom settings.xml used to benefit from ACP causing unexpected pluginRepository order.

@MarkEWaite MarkEWaite changed the title [ci.jenkins.io] Use the jenkins-infra's Artifact Caching Proxy to benefit from cached artefacts [ci.jenkins.io] Use the jenkins-infra's Artifact Caching Proxy to benefit from cached artifacts Sep 21, 2023
@basil
Copy link
Member

basil commented Sep 21, 2023

Should this issue be transferred to jenkins-infra/helpdesk?

@dduportal
Copy link
Contributor Author

Should this issue be transferred to jenkins-infra/helpdesk?

I hesitated to be honest. The scope (project maven-hpi-plugin) makes sense to have the issue here, but having it in jenkins-infra/helpdesk would ensure tracking (or at least not being forgotten) by the infra team.

@basil
Copy link
Member

basil commented Sep 21, 2023

OK, maybe we can have two tickets then, each one linking to the other, to cover both cases?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants