But what about when the slave is not installed as a service? I use headless jnlp (https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Launchslaveagentheadlessly) in a script that makes sure slave.jar is up to date.
It looks like should be able to authenticate with -auth or –jnlpCredentials, but neither seems to work - ideally, I’d like to use my API token rather than my password … Is this supposed to work, or is this a request for a new feature? From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kohsuke Kawaguchi Sent: 11 January 2013 14:16 To: jenkinsci-users@googlegroups.com Subject: Re: JNLP slave no longer works Slaves installed as a service stores the secret token information in the startup configuration file, such as /etc/init/jenkins-slave-*.conf (Linux), /System/Library/LaunchDaemons/org.jenkins-ci.slave.*.plist (OS X), or $SLAVE_ROOT/jenkins-slave.xml (Windows). Look for seemingly meaningless hex-encoded token in this file (which is passed as an argument to the the Java program). Now download the JNLP file again for that slave from Jenkins Web UI, then look for a similar seemingly meaningless hex-encoded token in that file. Overwrite the local version with what's now in JNLP, and it'd be good to go. If you aren't sure, you can also simply re-install the slave agent again. Existing slave agent will do no harm since it will not be able to connect back. 2013/1/11 <stuart.gr...@doccentrics.com<mailto:stuart.gr...@doccentrics.com>> Thanks for the info, but how is this change applied to a linux slave? On Tuesday, 8 January 2013 02:50:39 UTC, Kohsuke Kawaguchi wrote: This is unfortunately a necessary measure. See the "Fix" section in https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 -- Kohsuke Kawaguchi -- Kohsuke Kawaguchi -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
