-
Improvement
-
Resolution: Fixed
-
Minor
-
None
It is almost one year since the release of JNLP4 protocol in Remoting 3.0. This protocol is available in Jenkins LTS since 2.32.1, and so far it demonstrates good stability being compared to JNLP2 and especially to JNLP3. The protocol was enabled by default in 2.46.x, and we do not have confirmed JNLP4 issues since that.
I propose to disable the previous protocols
- is related to
-
JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted
-
- Resolved
-
- links to
[JENKINS-45841] Disable JNLP1/JNLP2/CLI1 by default on new installations
Epic Link | New: JENKINS-38833 [ 175240 ] |
Remote Link | New: This issue links to "Proposal in the ML (Web Link)" [ 17356 ] |
Component/s | New: remoting [ 15489 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "https://github.com/jenkinsci/remoting/pull/183 (Web Link)" [ 17375 ] |
Remote Link | New: This issue links to "https://github.com/jenkinsci/remoting/pull/182 (Web Link)" [ 17376 ] |
Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins/pull/2950 (Web Link)" [ 17377 ] |
Code changed in jenkins
User: Oleg Nenashev
Path:
docs/protocols.md
http://jenkins-ci.org/commit/remoting/8374363405ed190ea3df89b5da25c887c58fd1f7
Log:
JENKINS-45841- Recategorize the protocolsNow there are 3 categories: Active, Deprecated and Test