I think that message means that the technique which is launching the slaves
as a windows service from the GUI is using JNLP.
The security advisory page on the wiki [1] says Slaves that are started
via Java Web Start will fail to reconnect if the *.jnlp file is locally
stored. This is because
I upgraded my Debian Jenkins LTS from 1.480.1 to 1.480.2 today using the Debian
package manager. The machine was running with authentication enabled and was
using Debian, CentOS, Red Hat, and Windows slave agents. The Linux slave
agents are launched with ssh. The Windows slave agents are
Hi Mark,
On 07/01/2013 18:21, Mark Waite wrote:
I upgraded my Debian Jenkins LTS from 1.480.1 to 1.480.2 today using the
Debian package manager. The machine was running with authentication
enabled and was using Debian, CentOS, Red Hat, and Windows slave agents.
The Linux slave agents are
I have the same issue after upgrading from 1.480.1 to 1.480.2 on Ubuntu
12.04. I am able to launch the windows slaves manually, but unable to have
them run as a windows service from the gui. I am able to install it as a
service from the command line, but the master never connects to the slave.
