|
||||||||
|
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-16273) Slaves ... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)
- [JIRA] (JENKINS-16273) Sl... [email protected] (JIRA)

I have configured all of my Windows slave launching method from "Launch slave agents via Java Web Start" to "Let Jenkins control this Windows slave as a Windows service" to avoid this issue![]()
The remote management facility of Windows is hard for me to set correctly, I spent more than 6 hours to make all of my 6 Windows slaves run as well as before.