[JIRA] (JENKINS-43170) No credentials injected into managed settings.xml with Pipeline Maven Plugin

[reck...@yatta.de (JIRA)]

Title: Message Title

creckord created an issue   Jenkins / JENKINS-43170 No credentials injected into managed settings.xml with Pipeline Maven Plugin Issue Type: Improvement Assignee: Dominik Bartholdi Components: config-file-provider-plugin, pipeline-maven-plugin Created: 2017/Mar/28 5:33 PM Environment: Jenkins 2.32.3 Config File Provider Plugin 2.15.7 Pipeline Maven Integration Plugin 2.0 Priority: Minor Reporter: creckord I have a settings.xml that is managed by the Config File Provider Plugin and uses the option to inject stored credentials from the Jenkins credentials stores instead of having them directly in the settings.xml. I'm using this settings.xml in a withMaven block like this: withMaven(maven: 'Maven', mavenSettingsConfig: 'default-settings', mavenLocalRepo: '.repo') {    sh 'mvn help:effective-settings' } I would have expected that the effective settings would contain <server> sections for the configured credentials, but they don't. All static content from the managed settings.xml is present though. I've marked this as Improvement instead of Bug, since https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin indicates that this might be expected: The file types 'Global Maven settings.xml' and 'Maven settings.xml' have built-in support for the Credentials Plugin. When the plugin serves the settings.xml to the maven execution, the credentials get injected. This functionality is only available in the maven builder (e.g. for freestyle projects) and maven project type. Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.