Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40700

Display communication protocol in agent logs

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            core/src/main/resources/hudson/cli/CliProtocol/description.jelly
            core/src/main/resources/hudson/cli/CliProtocol/description.properties
            core/src/main/resources/hudson/cli/CliProtocol2/description.jelly
            core/src/main/resources/hudson/cli/CliProtocol2/description.properties
            core/src/main/resources/hudson/cli/Messages.properties
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol/description.jelly
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol/description.properties
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol/description_sr.properties
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol2/description.jelly
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol2/description.properties
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol2/description_sr.properties
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol3/description.jelly
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol3/description.properties
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol3/description_sr.properties
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol4/description.jelly
            core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol4/description.properties
            core/src/main/resources/jenkins/slaves/Messages.properties
            http://jenkins-ci.org/commit/jenkins/0c991dec38800adabacd8a56349bd61575c1d7e5
            Log:
            Merge pull request #2682 from samrocketman/enhance-slave-protocol-descriptions

            JENKINS-40700 Enhance slave protocol descriptions

            Compare: https://github.com/jenkinsci/jenkins/compare/8820a55dc670...0c991dec3880

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/hudson/cli/CliProtocol/description.jelly core/src/main/resources/hudson/cli/CliProtocol/description.properties core/src/main/resources/hudson/cli/CliProtocol2/description.jelly core/src/main/resources/hudson/cli/CliProtocol2/description.properties core/src/main/resources/hudson/cli/Messages.properties core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol/description.jelly core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol/description.properties core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol/description_sr.properties core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol2/description.jelly core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol2/description.properties core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol2/description_sr.properties core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol3/description.jelly core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol3/description.properties core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol3/description_sr.properties core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol4/description.jelly core/src/main/resources/jenkins/slaves/JnlpSlaveAgentProtocol4/description.properties core/src/main/resources/jenkins/slaves/Messages.properties http://jenkins-ci.org/commit/jenkins/0c991dec38800adabacd8a56349bd61575c1d7e5 Log: Merge pull request #2682 from samrocketman/enhance-slave-protocol-descriptions JENKINS-40700 Enhance slave protocol descriptions Compare: https://github.com/jenkinsci/jenkins/compare/8820a55dc670...0c991dec3880
            Hide
            marko_andrijevic Marko Andrijevic added a comment -

            Hi Oleg Nenashev, I see some actions have been taken on this issue but it's still Opened. Can you please let us know what's the latest on it? Is there a plan to fix it or it'll get closed without resolution?

            Thanks,
            Marko

            Show
            marko_andrijevic Marko Andrijevic added a comment - Hi Oleg Nenashev , I see some actions have been taken on this issue but it's still Opened. Can you please let us know what's the latest on it? Is there a plan to fix it or it'll get closed without resolution? Thanks, Marko
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Marko Andrijevic I have a plan to work on logging stories once I get bits in JENKINS-44108 landed

            Show
            oleg_nenashev Oleg Nenashev added a comment - Marko Andrijevic I have a plan to work on logging stories once I get bits in JENKINS-44108 landed
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            But you can create a pull request, this change is pretty trivial. If there is a PR, I will try to review and integrate it ASAP

            Show
            oleg_nenashev Oleg Nenashev added a comment - But you can create a pull request, this change is pretty trivial. If there is a PR, I will try to review and integrate it ASAP
            Hide
            liketic Li Ke added a comment -

            Oleg Nenashev I can work on this. Just want to know, where can I find the protocol variable. Thanks.

            Show
            liketic Li Ke added a comment - Oleg Nenashev I can work on this. Just want to know, where can I find the protocol variable. Thanks.

              People

              • Assignee:
                vulong237 Long Nguyen
                Reporter:
                sag47 Sam Gleske
              • Votes:
                2 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: