-
Bug
-
Resolution: Fixed
-
Blocker
-
1.498+, Windows Server 2008 R2
All of my windows salve cannot connect to Jenkins master after upgrading to 1.498. Following messages showed up in slaves' jenkins-slave.err:
java.io.IOException: Failed to load http://192.168.30.95/jenkins/computer/Fortify%201/slave-agent.jnlp: 403 Forbidden
at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:238)
at hudson.remoting.Launcher.run(Launcher.java:200)
at hudson.remoting.Launcher.main(Launcher.java:173)
- depends on
-
JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
-
- Closed
-
-
JENKINS-4071 jnlp slaves doesn't support HTTP Auth
-
- Closed
-
- is duplicated by
-
JENKINS-16346 Upgrade to Jenkins ver. 1.499 breaks master/slave connection
-
- Resolved
-
-
JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp
-
- Closed
-
- is related to
-
JENKINS-14610 Full Admin rights needed to run slave WebStart
-
- Resolved
-
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly
http://jenkins-ci.org/commit/jenkins/a1e709ddf0ca48b25ad07ee13a2fbdb0a6d97c0e
Log:
JENKINS-16273Improved instructions for passing -jnlpCredentials.First, display instructions when the user has CONNECT, not necessarily ADMINISTER.
Second, when anonymous users cannot CONNECT, show how to use -jnlpCredentials
(and do not bother showing javaws, since it does not work in this case).