Use "*Let Jenkins control this Windows slave as a Windows service*"
You'll need to provide a user able to remote log in to the slave.
Then you can choose whether you want to install the service as the Local
System, as the administrator account, or as another account.
Vincent
2012/11/14 Diogo Gue
>"On recent Jenkins (~>1.450) you can install windows slave directly from
>Jenkins (and run it using a specific user if required), you don't need to use
>JNLP anymore."
>
>How should I configure the node then?
We always configure slaves via SSH.
- Andrew
"On recent Jenkins (~>1.450) you can install windows slave directly from
Jenkins (and run it using a specific user if required), you don't need to
use JNLP anymore."
How should I configure the node then?
--Diogo
On Wed, Nov 14, 2012 at 10:29 PM, Vincent Latombe wrote:
> Hello,
>
> On recent J
Hello,
On recent Jenkins (~>1.450) you can install windows slave directly from
Jenkins (and run it using a specific user if required), you don't need to
use JNLP anymore, and slave.jar is updated each time you restart the master
(each time the master connects to the slave to start its service actu
Don't know how it happens with JNLP, but for Linux machines (over SSH).
It will update it automatically, when ever slave.jar is updated on master
and connection (ssh) is restarted.
PS: If you see connection logs (on the Jenkins UI), you will see it
updating the slave.jar file.
Thanks
On Wed, Nov
Hi, out setup we have two types of slaves:
- windows through jnlp with a windows service.
- linux with ssh.
On the windows ones we had to download the jenkins windows version and
configure the jenkins-slave.xml and then we only have the jenkins-slave
service to start and not the jenkins maste
