-
Improvement
-
Resolution: Fixed
-
Minor
-
Jenkins ver. 2.38
It would be nice if the Jenkins startup log for permanent slaves would output what protocols it was using to communicate with the master.
Current behavior
Right now the startup log looks something like:
JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online
Desired output
Underneath Slave.jar version would be a good place to output the communication protocol. Something along the lines of:
JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 Communication Protocol: Java Web Start Agent Protocol/4 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online
Using the protocol getDisplayName() method.
- relates to
-
JENKINS-36871 JNLPProtocol4
-
- Closed
-
- links to
[JENKINS-40700] Display communication protocol in agent logs
Link |
New:
This issue relates to |
Description |
Original:
It would be nice of the Jenkins startup log for permanent slaves would output what protocols it was using to communicate with the master. h1. Current behavior Right now the startup log looks something like: {code:none} JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online {code} h1. Desired output Underneath {{Slave.jar version}} would be a good place to output the communication protocol. Something along the lines of: {code:none} JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 Communication Protocol: Java Web Start Agent Protocol/4 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online {code} Using the protocol {{getDisplayName()}} method. |
New:
It would be nice if the Jenkins startup log for permanent slaves would output what protocols it was using to communicate with the master. h1. Current behavior Right now the startup log looks something like: {code:none} JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online {code} h1. Desired output Underneath {{Slave.jar version}} would be a good place to output the communication protocol. Something along the lines of: {code:none} JNLP agent connected from localhost/127.0.0.1 Slave.jar version: 3.3 Communication Protocol: Java Web Start Agent Protocol/4 This is a Unix agent NOTE: Relative remote path resolved to: /home/sam/sandbox/jenkins Agent successfully connected and online {code} Using the protocol {{getDisplayName()}} method. |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Epic Link | New: JENKINS-38833 [ 175240 ] |
Epic Link | Original: JENKINS-38833 [ 175240 ] |
New:
|
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
Labels | New: diagnostics newbie-friendly |
Assignee | New: Long Nguyen [ vulong237 ] |
Assignee | Original: Long Nguyen [ vulong237 ] | New: Akihiro [ aki7m ] |
Remote Link | New: This issue links to "Remoting PR-452 includes the protocol info in release 4.9 and later (Web Link)" [ 26898 ] |