Of
stuart.gr...@doccentrics.com
Sent: 11 January 2013 10:39
To: jenkinsci-users@googlegroups.com
Subject: Re: JNLP slave no longer works
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
Webber
*From:* jenkins...@googlegroups.com javascript: [mailto:
jenkins...@googlegroups.com javascript:] *On Behalf Of *
stuart...@doccentrics.com javascript:
*Sent:* 11 January 2013 10:39
*To:* jenkins...@googlegroups.com javascript:
*Subject:* Re: JNLP slave no longer works
:* Re: JNLP slave no longer works
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
The slave.jar from LTS 1.480.2 version has parameters -auth and
-jnlpCredentials. Neither of them seems to work, I will get a Exception
in thread main java.lang.NoClassDefFoundError:
org/apache/commons/codec/binary/Base64 or java.io.IOException: Failed to
load
On 13-01-11 05:55 AM,
matthew.web...@diamond.ac.uk wrote:
Fixed by going to Manage Jenkins - Configure Global Security, and under
Project-based Matrix Authorization Strategy I had to enable “connect” in the
“slave” section, for user “Anonymous”.
IIUC, that's going to leave your Jenkins
On Fri, Jan 11, 2013 at 7:12 AM, Brian J. Murrell br...@interlinx.bc.ca wrote:
Fixed by going to Manage Jenkins - Configure Global Security, and under
Project-based Matrix Authorization Strategy I had to enable “connect” in the
“slave” section, for user “Anonymous”.
IIUC, that's going to
On 13-01-11 08:44 AM, Les Mikesell wrote:
Doesn't the connecting node name already have to be configured in
jenkins
Sure. But if anonymous read is allowed, anyone can see the node names.
- and not already connected?
Is disconnecting a node really that difficult? You could try attacking
a
Yes, you just need to re-download the JNLP file from the master and
overwrite the local copy at the slave.
2013/1/7 Jon Schewe jpsch...@mtu.net
OK, so if I just keep the jnlp local now instead of always requesting it
on startup, thing will continue to work, correct?
On Monday, January 7,
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
Agree with Brian here. Only do it when you are trusting the users of the
network.
2013/1/11 Brian J. Murrell br...@interlinx.bc.ca
On 13-01-11 05:55 AM,
matthew.web...@diamond.ac.uk wrote:
Fixed by going to Manage Jenkins - Configure Global Security, and
under Project-based Matrix
If you want to be able to add slaves without configuring them first on the
master, you can use the swarm slave plugin.
2013/1/11 Les Mikesell lesmikes...@gmail.com
On Fri, Jan 11, 2013 at 7:12 AM, Brian J. Murrell br...@interlinx.bc.ca
wrote:
Fixed by going to Manage Jenkins - Configure
:
jenkinsci-users@googlegroups.com] *On Behalf Of *
stuart.gr...@doccentrics.com
*Sent:* 11 January 2013 10:39
*To:* jenkinsci-users@googlegroups.com
*Subject:* Re: JNLP slave no longer works
** **
** **
Thanks for the info, but how is this change applied to a linux slave?
On Tuesday
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
2013/1/11 SBreitbach steffen.breitb...@1und1.de
The slave.jar from LTS 1.480.2 version has parameters -auth and
-jnlpCredentials. Neither of them seems to work, I will get a Exception
in thread main java.lang.NoClassDefFoundError:
org/apache/commons/codec/binary/Base64 or java.io.IOException:
We'll fix this in the next mainline release, and once all the fallout bugs
like this are fixed and verified, I'll plan on another LTS release.
My apologies for the problems in the mean time.
No problem! The workaround using the anonymous user is OK for me in the
meantime. :)
smime.p7s
I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer
connect. I get an error:
JNLPException[category: Download Error : Exception: java.io.IOException:
Server returned HTTP response code: 403 for URL:
https://server:8010/computer/slave-jnlp/slave-agent.jnlp : LaunchDesc: null
]
This is unfortunately a necessary measure.
See the Fix section in
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04
2013/1/7 Jon Schewe jpsch...@mtu.net
I just upgraded to 1.480.2 from 1.471 and my JNLP slaves can no longer
connect. I get an error:
OK, so if I just keep the jnlp local now instead of always requesting it on
startup, thing will continue to work, correct?
On Monday, January 7, 2013, Kohsuke Kawaguchi wrote:
This is unfortunately a necessary measure.
See the Fix section in
18 matches
Mail list logo
