Artifacts proxy does not deliver incremental jars about helpdesk HOT 6 CLOSED

I'm not sure if this is related, but two of my builds fail with a strange error that indicates that a maven artifact is not found:

• https://ci.jenkins.io/job/Plugins/job/analysis-model/job/PR-1039/1/pipeline-console/?selected-node=33
• https://ci.jenkins.io/job/Plugins/job/analysis-model/job/PR-1035/3/pipeline-console/?selected-node=41

from helpdesk.

Thanks for reporting it @uhafner . @basil found the same issue while creating the most recent release of the plugin bill of materials. He reported it as:

• #4021

I believe there is a short-term workaround that you can apply to your pull requests. Label them with skip-artifact-caching-proxy and the artifact caching proxy should be skipped.

from helpdesk.

The only thing I can add for now is the content of the settings.xml we're using for ACP (that's a template but you'll get the gist of it):
https://github.com/jenkins-infra/jenkins-infra/blob/production/dist/profile/templates/jenkinscontroller/casc/artifact-caching-proxy.yaml.erb

I don't know yet if the issue is related or not to the addition of the plugin repositories profile: https://github.com/jenkins-infra/jenkins-infra/pull/3041/files

from helpdesk.

For info, we changed the behavior of the Artfact Caching Proxy ("ACP") in #3969 earlier today with a new 1.0.0 version.

This 1.0.0 feature a new resolution mechanism: ACP now tries to get the requested artifact from Jenkins public or falls back to Jenkins incremental and then Maven central. It implies a change in the settings.xml to unify to only "1 mirror".

It means Maven no longer retry on multiple mirrors (e.g. resolution has different implementation when using ACP on ci.jenkins.io compared to developer workstation) but ACP does with the same order.

@uhafner could you retry (as the PR was merged and it was quite some time ago) to see if the new behavior works as expected? We see incremental artifacts being available (and cached except the maven-metadata.xml) by ACP instances now so it should work better to your expectation

from helpdesk.

Hello @uhafner @MarkEWaite , the problem should be fixed. https://ci.jenkins.io/job/Plugins/job/analysis-model/job/PR-1039/2/ is now passing.

Can you check if you can reproduce the "incrementals not in ACP" behavior (e.g. the original subject of this issue)?

from helpdesk.

It looks like this issue is resolved as per #4021 (comment).

As such I am closing the issue. Thanks all!

Please feel free to reopen if I am mistaken or if the problem re-surface.

from helpdesk.