-
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
-
[JENKINS-16273] Slaves forbidden to request JNLP anonymously but -jnlpCredentials not offered
Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
Attachment | New: jenkins-slave-error.jpg [ 23033 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Not A Defect [ 7 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Environment | Original: Windows Server 2008 R2 | New: 1.498+, Windows Server 2008 R2 |
Labels | New: jnlp regression security slave | |
Summary | Original: Slaves cannot connect to master through JNLP after upgrading to 1.498 | New: Slaves forbidden to request JNLP anonymously but no clear way to pass API token |
Link | New: This issue is blocking SECURITY-49 [ SECURITY-49 ] |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue depends on |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue depends on |