[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but no clear way to pass API token

[jesper.klit.jen...@intelligrated.com (JIRA)]

Jesper Jensen commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but no clear way to pass API token Based up @Trevor and @Richard instructions here is how I got the windows slaves to run as a service again: 1 - Uninstall the service if it exists 2 - Delete the old jenkins-slave.exe and jenkins-slave.xml 3 - Start the web client and let it install the service 4 - Download the slave-agent.jnlp to the directory where the jenkins-slave.exe is 5 - Edit the jenkins-slave.xml so the it looks like this the important part is the file:///%BASE% <arguments>-Xrs -jar "%BASE%\slave.jar" -jnlpUrl file:///%BASE%/slave-agent.jnlp</arguments> 6 - Stop your web client if it not already and restart your service. Mine are now running. Disclaimer: I haven't studied the security implications of storing slave-agent.jnlp at that location in the slave. I suspect it is fine but it would be good if someone could comment on whether there is a better location. Also not sure how the jnlp file gets updated if needed.

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