-
Bug
-
Resolution: Fixed
-
Minor
-
None
This is rather annoying as you need custom configuration to talk to Jenkins (because of preemptive authentication).
I have server configuration like this:
<server>
<id>jenkins</id>
<configuration>
<wagonProvider>httpclient</wagonProvider>
<httpConfiguration>
<all>
<usePreemptive>true</usePreemptive>
</all>
</httpConfiguration>
</configuration>
</server>
but after injecting the credentials the configuration element is gone (checked with help:effectiv-settings)
<server> <id>jenkins</id> <username>jenkins</username> <password>****</password> </server>
Workaround is to use the "Mask passwords plugin" and inject the password as an env. variable
- duplicates
-
JENKINS-39991 Credential replacement in settings.xml losts configuration, filePermissions and directoryPermissions elements
- Closed