|
||||||||
|
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-13735) Jenkins starts w... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... [email protected] (JIRA)

I deployed the jenkins v1.470 today and tested the fis. Works like a charm!!!
No irrelevant slaves are powered up, the correct slave required to execute a job is started.
Thanks to everyone for the fast responses to my problem!
@Jason: thanks for your analysis and fix!
Cheers, Marco.