|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15774) Add ability to spec... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)
- [JIRA] (JENKINS-15774) Add ability to... [email protected] (JIRA)

who ever is gonna implement this, I think a good solution would be to implement this the same way as we did for maven, using the config-file-provider [1] plugin to administrate the settings file - this way a user/admin is not only able to reference a settings file, but also to change it in the browser.
The ivy plugin could just implement a org.jenkinsci.lib.configprovider.model.Config and access it during execution. Have a look at org.jenkinsci.plugins.configfiles.xml.XmlConfig or org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig
[1] https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin