-
Improvement
-
Resolution: Fixed
-
Minor
-
None
When troubleshooting the connectivity of JNLP build agents, it'd be nice if the TcpSlaveAgentListener provides more diagnosability. Currently, a protocol is binary, so it prevents the standard diagnostic tools like 'nc' and 'telnet' to work.
The situation where this gets frustrating is when you have network middle layers, such as port forwarder, iptables, and other such things. A basic "Ping? Pong!" would help users perform trouble-shooting quickly.
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
core/src/main/java/hudson/TcpSlaveAgentListener.java
test/src/test/java/hudson/TcpSlaveAgentListenerTest.java
http://jenkins-ci.org/commit/jenkins/172df6a7dfca56477c471c381687599c80f5113b
Log:
[FIXED JENKINS-37223]
Added a simple diagnostic HTTP response to the TcpSlaveAgentListener.