-
Bug
-
Resolution: Fixed
-
Minor
The port is being used for CLI and some non-JNLP protocols outside Jenkins core. E.g.
- "JNLP agent listener started on TCP port {0}"
- "Failed to accept JNLP agent connections"
- ...
- JNLP Port in UI
[JENKINS-44103] TcpSlaveAgentListener prints "JNLP connection" in some messages when it is not JNLP
Epic Link | New: JENKINS-44099 [ 181725 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Labels | New: newbie-friendly |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: newbie-friendly | New: lts-candidate newbie-friendly |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Code changed in jenkins
User: Oleg Nenashev
Path:
core/src/main/java/hudson/TcpSlaveAgentListener.java
core/src/main/resources/hudson/TcpSlaveAgentListener/index.jelly
http://jenkins-ci.org/commit/jenkins/b5fe89cc9873a1c16c580ced43054b62ef70589b
Log:
JENKINS-44103- Cleanup usages of the "JNLP" term in TcpSlaveAgentListener