-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins ver. 2.150.1
Problem reproduce steps:
- Credentials > System > Add Domain A, just has name specified.
- In domain A, add a credential C, username: maven repo username, password: maven repo password.
- Manage Jenkins > Managed files, create a maven global settings.xml M, add Server Credentials using credential C.
- Create a Multibranch pipeline, in Pipeline Maven Configuration section, using config M.
- Run pipeline.
Build log:
[withMaven] using Maven global settings.xml '876cdf5c-802b-4252-a062-4b9d8602dd06' with NO Maven servers credentials provided by Jenkins
If I create credential C and maven global settings.xml M inside Multibranch pipeline, everything goes fine:
[withMaven] using Maven global settings.xml 'f657ec5c-cc63-4730-a133-7e58c3ea433a' with Maven servers credentials provided by Jenkins (replaceAll: true): [mavenServerId: 'supwisdom-snapshots', jenkinsCredentials: '250947bb-2ce2-4cf5-b62f-bba7e2af7df0', username: 'deployment', type: 'UsernamePasswordCredentialsImpl'], [mavenServerId: 'supwisdom-releases', jenkinsCredentials: '250947bb-2ce2-4cf5-b62f-bba7e2af7df0', username: 'deployment', type: 'UsernamePasswordCredentialsImpl']
cleclerc That's weird, please take a look at screenshot i uploaded. Credentials are listed when define global maven settings.
BTW, everything goes fine on Jenkins ver. 2.138.3
— update —
I followed your suggestion not using generated ids for credentials and maven settings. Problem solved.