I figured out the reason it wasn't presenting the slave-agent.jnlp at http://<master jenkins>/computer/<node>/ was because I had selected to bring the node online at a scheduled time, and it wasn't scheduled to be up, once it was online I could download it and re-install.
On Wednesday, May 8, 2013 6:50:12 AM UTC-5, Brian Johnson wrote: > > I was trying to move the jenkins directory on my windows slave and ran > into a problem when I found that the slave-agent.jnlp that I had used to > start and intall was deleted. > > So the issue is how do I get the jenkins master to re-supply the > slave-agent.jnlp that it originally supplied when I first navigated to > http://<master jenkins>/computer/<node>/? > > I tried re-constructing the slave-agent.jnlp, but the issue is that > security is turned on and I don't have the "secret key" passed as the first > argument to hudson.remoting.jnlp.Main. > -- 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.
