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

Computer.getHostName fails when it could work

XMLWordPrintable

    • Icon: Patch Patch
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None

      As discussed in http://n4.nabble.com/Hudson-and-Selenium-Unable-to-determine-the-host-name-Skipping-Selenium-execution-tp956619p956791.html some operations and plugins can fail due to the way Computer.getHostName works - basically Hudson thinks it is unable to ping a slave even though the slave really is reachable from the master.

      This patch turns the way a slave is pinged into an extension point so people can implement custom ways of pinging - for example calling out to the ping command of the OS. An implementation of the extension point is included that maintains the current mechanism, so by default there should be no change in behavior.

      The extension-point/default-implementation approach follows the pattern of the ssh-slaves plugin, which uses an extension point in locating a JVM on the slave.

            Unassigned Unassigned
            nparry Nathan Parry
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: