|
||||||||
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... johno.crawf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... johno.crawf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... johno.crawf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... egues...@java.net (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... johno.crawf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... egues...@java.net (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... johno.crawf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... egues...@java.net (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... egues...@java.net (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... egues...@java.net (JIRA)
- [JIRA] (JENKINS-15774) Add ability to spec... johno.crawf...@gmail.com (JIRA)
In our system all jobs are using the same set of ivy settings no matter where they are built (master or slave) So there is no need to specify this for every slave we have. I.e. there is no "slave specific" configuration in that regard, if i understood your comment properly.