[JIRA] (JENKINS-16273) Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered

[jgl...@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-16273 Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered Tested workaround for the combination of this and JENKINS-9679 in 1.480.2 for Windows service users on XP: Remove any existing service. (jenkins-slave.exe uninstall or see http://stackoverflow.com/a/197941/12916 for removing the service entry; and delete the slave directory.) From Windows slave machine, log in, browse to slave page, and click on the JNLP launch button; slave should start. Request Windows service installation. Stop service if you started it. (Control Panel » Admin Tools » Services) Copy your downloaded jenkins-slave.jnlp somewhere permanent, such as the slave FS root. Open jenkins-slave.xml in Notepad, find the -jnlpUrl, and change it to point to the downloaded JNLP. This will be a file-protocol URL and must use forward slashes like any URL, e.g.: -jnlpUrl file:/C:/jenkins/slave-agent.jnlp Start service. The slave should now be connected, and should reconnect properly after a reboot.

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