On 20/02/2013 17:29, Les Mikesell wrote:
On Wed, Feb 20, 2013 at 11:19 AM, Richard Mortimer
<[email protected]> wrote:
The main breakage for jnlp slaves was that they tried to download the
authentication token on each startup. This is no longer allowed so they need
to get the token by another means.
An easy way to do this is to download the token, in slave-agent.jnlp, (once)
for each slave and to save it on the slave. Then the windows service startup
script needs to be changed to reference this rather than downloading the
file each time it starts up.
Won't this mean that future updates to the slave jar won't get pushed
to the slaves?
I didn't think that access to slave.jar had been changed by the security
fix. I can still access it at
http://jenkins.url/jnlpJars/slave.jar
e.g.
http://ci.jenkins-ci.org/jnlpJars/slave.jar
The only change that I believe is needed for the workaround is the
location of slave-agent.jnlp all other bits are unchanged.
Regards
Richard
P.S. It is true that slave.jar is stored locally on my system. I don't
know why that is or whether newer windows installs do thing differently
there. I just periodically update slave.jar manually - normally when
things seem to break! But that hasn't changed with the latest security
stuff to my knowledge.
--
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.
