We have 2 instances of Jenkins running:

• 1 very old v2.46.3 with maven-plugin 2.15.1
• A current v2.263.2 with m-p 3.8

I've been trying to migrate our users to the newer Jenkins for some time and am now talking with the few stragglers about their reasons. So I found that some don't want to migrate because uploading their Maven Artifacts makes their build 3-4 as slow as on the old version.

So, I've been looking into this and it appears that on the newer Jenkins with the newer plugin, the traffic is being routed over our proxy – which should not be.

When Maven uploads directly to our Repo, it uses the proxy configuration from the settings.xml, which has an exclusion for our internal servers. We use this settings.xml on all our Jenkins nodes (both masters and all agents), so the configuration is the same everywhere.

So, why is the new version of the plugin using my proxy, but not the exclusion anymore?