Which version are you using for the pipeline-maven-plugin and config-file-provider?
- pipeline-maven-plugin: 3.10.0
- config-file-provider: 3.8.2
In the sample you shared you configured the settings as Default global settings provider in the tools configuration ? No as Default settings provider?
According to how I interpreted this plugin's documentation, the only "default" thing the plugin will fall back on when calling withMaven() without specifying additional (optional) parameters is the "global" one. But that could just be missing documentation. In any case, I've tried it with global only, user only and both. I get the same results all three ways. In the example output above, I had both specified with the same information in both managed files as a desperate attempt to debug this issue by trial and error.
The plugin output in the logs didn't even mention the user config.
[2021-12-16T14:41:48.652Z] [withMaven] using Maven global settings.xml 'global-maven-settings' with Maven servers credentials provided by Jenkins (replaceAll: false): [mavenServerId: 'com.myinternal.repo.releases', jenkinsCredentials: '7ad2488b-6087-4727-a1ca-6b9ced57baa6', username: 'ci', type: 'UsernamePasswordCredentialsImpl'], [mavenServerId: 'com.myinternal.repo.snapshots', jenkinsCredentials: '7ad2488b-6087-4727-a1ca-6b9ced57baa6', username: 'ci', type: 'UsernamePasswordCredentialsImpl']
Note that the "global" settings are mentioned (with credentials even being correctly called out) but the "user" settings are entirely ignored even though (by Maven design) the "user" settings should override the "global" settings. Nevertheless, I assumed this was by plugin design since the documentation more or less says as much.
In any case, even though that log line clearly states that it found the settings and parsed them (including credentials), nothing actually shows up in the effective settings inside withMaven() execution scope.