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

Display communication protocol in agent logs

    XMLWordPrintable

Details

    • 2.343

    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

            sag47 Sam Gleske created issue -
            sag47 Sam Gleske made changes -
            Field Original Value New Value
            Link This issue relates to JENKINS-36871 [ JENKINS-36871 ]
            sag47 Sam Gleske made changes -
            Description 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.
            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.
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Link JENKINS-38833 [ 175240 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Link JENKINS-38833 [ 175240 ] JENKINS-46154 [ 184393 ]
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels diagnostics newbie-friendly
            vulong237 Long Nguyen made changes -
            Assignee Long Nguyen [ vulong237 ]
            aki7m Akihiro made changes -
            Assignee Long Nguyen [ vulong237 ] Akihiro [ JIRAUSER131889 ]
            markewaite Mark Waite made changes -
            Remote Link This issue links to "Remoting PR-452 includes the protocol info in release 4.9 and later (Web Link)" [ 26898 ]
            basil Basil Crow made changes -
            Released As 2.343
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Fixed but Unreleased [ 10203 ]
            basil Basil Crow made changes -
            Status Fixed but Unreleased [ 10203 ] Resolved [ 5 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

            People

              aki7m Akihiro
              sag47 Sam Gleske
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: