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

Based up @Trevor and @Richard instructions here is how I got the windows slaves to run as a service again:
1 - Stop service
2 - Uninstall the service if it exists dos (sc delete jenkinsslave-C__Jenkins)
3 - Delete the old jenkins-slave.exe, slave.jar and jenkins-slave.xml
4 - Start the web client and let it install the service
5 - Edit the jenkins-slave.xml so the it looks like this the important part is the jnlpCredentials <arguments>-Xrs -jar "%BASE%\slave.jar" -jnlpCredentials <user>:<password> -jnlpUrl http://<your server>/computer/<slave name>/slave-agent.jnlp</arguments></arguments>
6 - Stop your web client if it not already and restart your service.
Mine are now running.