Hello, Previously, with Jenkins 1.40x.x, when adding a new slave, I would log in to the slave and use the command provided to me. Something like: java -jar slave.jar <etc...>
With that, I would be given the opportunity to add the slave process as a service. Now, the command includes the -secret <big-identifier>, which is OK with me, but I'm never given the opportunity to add the slave as a service. The old service entry is totally incompatible. The old service entry executes a "jenkins-slave.exe" which, apparently, is no longer used (at least, I didn't get one when I executed the command java -jar slave.jar <http://10.95.16.106:8080/jnlpJars/slave.jar> -jnlpUrl http://##.##.##.##:8080/computer/SLAVE_NAME/slave-agent.jnlp -secret xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ). If it matters, my master is Linux and my slaves are Windows. >From the master, I tried to "Let Jenkins control this Windows slave as a >Windows service", but that didn't work. In fact, the master tried and failed to authenticate so many times, it locked my slave's user account (really not good at all :-(). So, I'd like to go back to how things worked before. Each slave had a jenkinsslave-C__Jenkins service. Thanks in advance. Steve K. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
