|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
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/groups/opt_out.
Hello,
sorry, I think I have to reopen this issue. It is still reproducible in Freestyle build jobs: Create such a job, add a Maven build step and set a settings.xml managed by "config file provider plugin".
I debugged on this and identified the problem: After clicking "Save", the settings are de-serialized correclty on the server side, but are overwritten with presumably fallback-values right after that. The fallback values should be available through the constructor of the "Maven" class although. With my fix it works for me: https://github.com/jenkinsci/jenkins/pull/833