|
||||||||
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 wrong slave for job restricted to specific one
m.lehn...@meditec.zeiss.com (JIRA) Thu, 14 Jun 2012 00:31:23 -0700
- [JIRA] (JENKINS-13735) Jenkins starts w... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... jsiir...@java.net (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... m.lehn...@meditec.zeiss.com (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... jswa...@alohaoi.com (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... m.lehn...@meditec.zeiss.com (JIRA)
- [JIRA] (JENKINS-13735) Jenkins sta... m.lehn...@meditec.zeiss.com (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.