You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For historical reasons, Jenkins still ships with old, deprecated protocols, JNLP1-connect, JNLP2-connect, and JNLP3-connect. These all have fundamental issues and known bugs. They were all superseded by the JNLP4-connect protocol released in Jenkins 2.27 over three years ago (October 2016). They have all been deprecated and unsupported since Jenkins 2.75 over two years ago. Since then there have been UI messages and an administrative monitor strongly discouraging their use. (See more information about the protocols at https://github.com/jenkinsci/remoting/blob/master/docs/protocols.md )
These protocols should be removed as part of cleaning up technical debt.
For historical reasons, Jenkins still ships with old, deprecated protocols, JNLP1-connect, JNLP2-connect, and JNLP3-connect. These all have fundamental issues and known bugs. They were all superseded by the JNLP4-connect protocol released in Jenkins 2.27 over three years ago (October 2016). They have all been deprecated and unsupported since Jenkins 2.75 over two years ago. Since then there have been UI messages and an administrative monitor strongly discouraging their use. (See more information about the protocols at https://github.com/jenkinsci/remoting/blob/master/docs/protocols.md )
These protocols should be removed as part of cleaning up technical debt.
Activity
jenkins-infra-bot commentedon Jan 10, 2020
Raw content of original comment:
jthompson Docker packaging will also need to be updated to close this story
jenkins-infra-bot commentedon Jan 10, 2020
Raw content of original comment:
Also created jenkins-infra/jenkins.io#2757 for the Administrative Monitors update