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

slave connection log should show when slave is successfully connected

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • None

    Description

      I'm filing this bug on behalf of an IRC user because it has confused me as well in the past, and would make an excellent "paper cut" to fix. If you are you trying to debug a slave issue and look at the log, the last thing you will see is likely something like:

      <===[HUDSON REMOTING CAPACITY]===>channel started
      Slave.jar version: 1.343
      This is a Unix slave
      Copied maven-agent.jar
      Copied maven-interceptor.jar
      Copied maven2.1-interceptor.jar

      with the AJAX thing still spinning (I assume because the slave is still running and as such still logging). However it is unclear that at this point the slave is successfully connected and functional. It would be really helpful to new Hudson users unsure if their setup is working to display a message in the log to the effect of "Slave successfully connected, will continue to log any errors" at this point!

      Attachments

        Activity

          Code changed in hudson
          User: : abayer
          Path:
          trunk/hudson/main/core/src/main/java/hudson/slaves/SlaveComputer.java
          http://jenkins-ci.org/commit/27457
          Log:
          [FIXED JENKINS-5630]

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : abayer Path: trunk/hudson/main/core/src/main/java/hudson/slaves/SlaveComputer.java http://jenkins-ci.org/commit/27457 Log: [FIXED JENKINS-5630]

          People

            abayer Andrew Bayer
            mcrooney mcrooney
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: