Slave Registered Remote Controls not identified in Jenkins Selenium Grid

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major
    • Component/s: selenium-plugin
    • None
    • Environment:
      Linux RHEL server
      Linux Ubuntu slave agent remote client

      I was attempting to rename the newest selenium-server-standalone-*.jar to replace the older one (as per some of the users posts).
      When I restarted the Jenkins server, the Selenium Grid page shows that the jenkins.nodeName is null for all of the connected remote contols clients (as shown below)

      {seleniumProtocol=Selenium, browserName=*firefox, maxInstances=5, jenkins.nodeName=}

      I put everything back the way it was, but this problem still exists, and the process for the hudson.remoting.Launcher of the selenium-server-standalone-*.jar is not running on the agents.

      Everything says that it should automatically configure and start when the Jenkins server is restarted.

            Assignee:
            Richard Lavoie
            Reporter:
            rejesi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: