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

Upgrade Selenium Grid Plugin to Selenium Grid 2.0

    Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: selenium-plugin
    • Labels:
      None

      Description

      Please upgrade Selenium in the plugin towards to Selenium Grid 2.0, as it seems to be pretty stable now and solved a number of issues.

      Selenium Grid 2 documentation: http://code.google.com/p/selenium/wiki/Grid2

        Issue Links

          Activity

          Hide
          salmira Tetiana Tvardovska added a comment -

          Upgrades for previous Selenium Grid releases were posted in the issue #JENKINS-6207.

          Show
          salmira Tetiana Tvardovska added a comment - Upgrades for previous Selenium Grid releases were posted in the issue # JENKINS-6207 .
          Hide
          salmira Tetiana Tvardovska added a comment - - edited

          Hi Kohsuke,

          please use this patch and release a new plugin version!

          Thank you in advance.

          By the way, when I tried to commit to SVN, I got an error:
          authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.java.net)

          Is it a normal SVN reaction here? Should I have rights for commit or no?

          Tatyana aka salmira.

          Show
          salmira Tetiana Tvardovska added a comment - - edited Hi Kohsuke, please use this patch and release a new plugin version! Thank you in advance. By the way, when I tried to commit to SVN, I got an error: authorization failed: Could not authenticate to server: rejected Basic challenge ( https://svn.java.net ) Is it a normal SVN reaction here? Should I have rights for commit or no? Tatyana aka salmira.
          Hide
          apgray apgray added a comment -

          +1
          I would like to be able to upgrade from Firefox 3.5 to 3.6. The only reason I have not done so is because Selenium Grid currently does not appear to support Firefox 3.6. Have tried the "updating the files in the JAR" fix to no avail.

          Thank you

          Show
          apgray apgray added a comment - +1 I would like to be able to upgrade from Firefox 3.5 to 3.6. The only reason I have not done so is because Selenium Grid currently does not appear to support Firefox 3.6. Have tried the "updating the files in the JAR" fix to no avail. Thank you
          Hide
          salmira Tetiana Tvardovska added a comment - - edited

          Patch for Selenium Grid 1.0.8 plugin was tested on Firefox 3.6.13 on Windows 7 and it works for me.
          Improvement:
          1. Selenium RC heartbeat functionality is also used now in the plugin (monitoring actual RC state and removing disconnected plugins from the list).

          Workaround that worked on my tested configuration:
          1. Hudson with Selenium Grid Plugin running Selenium Grid Hub 1.0.8 on Ubuntu 10.10.
          2. Selenium Grid Remote Control (RC) running on Windows 7 , started manually with the following command:

            ant -Dhost=rcWinHost -Dport=5558
               -DhubURL=http://hudsonHost:4444 
               -Denvironment="/windows/:*firefox"
               launch-remote-control
          

          As you see, I used environtment string as if it was automatically generated by the plugin RC-launcher.
          Make sure that desired browser could be launched from the command line. In my case, I get my Firefox 3.6.13 when I run from the command line:

          firefox
          

          The list of running RC at http://hudsonHost:8080/selenium/? included:

          Host Environment
          rcWinHost:5558 /windows/:*firefox

          3. Test was executed successfully for

          environment="windows:*firefox"
          Show
          salmira Tetiana Tvardovska added a comment - - edited Patch for Selenium Grid 1.0.8 plugin was tested on Firefox 3.6.13 on Windows 7 and it works for me. Improvement: 1. Selenium RC heartbeat functionality is also used now in the plugin (monitoring actual RC state and removing disconnected plugins from the list). Workaround that worked on my tested configuration: 1. Hudson with Selenium Grid Plugin running Selenium Grid Hub 1.0.8 on Ubuntu 10.10. 2. Selenium Grid Remote Control (RC) running on Windows 7 , started manually with the following command: ant -Dhost=rcWinHost -Dport=5558 -DhubURL=http://hudsonHost:4444 -Denvironment="/windows/:*firefox" launch-remote-control As you see, I used environtment string as if it was automatically generated by the plugin RC-launcher. Make sure that desired browser could be launched from the command line. In my case, I get my Firefox 3.6.13 when I run from the command line: firefox The list of running RC at http://hudsonHost:8080/selenium/? included: Host Environment rcWinHost:5558 /windows/:*firefox 3. Test was executed successfully for environment="windows:*firefox"
          Hide
          apgray apgray added a comment -

          Hi Salmira,

          I have a single machine currently running Windows 2003 Server SP2 (Not Windows 7) I am using Selenium Grid plugin to run my web tests.

          So I am letting Selenium Grid setup and tear down Firefox for each test. I can see this happening with Firefox 3.5 in the Task Manager. When I use FF 3.6 this does not happen. the Selenium Grid plugin seems to have issues talking to FF 3.6.

          Any hints on how I can get this to work in my environment?

          Show
          apgray apgray added a comment - Hi Salmira, I have a single machine currently running Windows 2003 Server SP2 (Not Windows 7) I am using Selenium Grid plugin to run my web tests. So I am letting Selenium Grid setup and tear down Firefox for each test. I can see this happening with Firefox 3.5 in the Task Manager. When I use FF 3.6 this does not happen. the Selenium Grid plugin seems to have issues talking to FF 3.6. Any hints on how I can get this to work in my environment?
          Hide
          salmira Tetiana Tvardovska added a comment -

          There is a special issue related to Firefox 3.6, please see JENKINS-5824 and see my reply there.

          Show
          salmira Tetiana Tvardovska added a comment - There is a special issue related to Firefox 3.6, please see JENKINS-5824 and see my reply there .
          Hide
          desperado Ruslan Strazhnyk added a comment - - edited

          Why do we need to support old from 1.0.8 (releases) or trunk(1.1.0)?
          These versions aren't very different from 1.0.7 and major problems are the same there.

          Dear Kohsuke, maybe it's better to switch to Selenium Grid 2.0 and upgrade plugin towards this version? Seems like it's pretty stable now.

          http://code.google.com/p/selenium/wiki/Grid2

          Show
          desperado Ruslan Strazhnyk added a comment - - edited Why do we need to support old from 1.0.8 (releases) or trunk(1.1.0)? These versions aren't very different from 1.0.7 and major problems are the same there. Dear Kohsuke, maybe it's better to switch to Selenium Grid 2.0 and upgrade plugin towards this version? Seems like it's pretty stable now. http://code.google.com/p/selenium/wiki/Grid2
          Hide
          salmira Tetiana Tvardovska added a comment -

          Totally agree that the plugin need to be updated to Selenium Grid 2.0. Such update would be more usefull.

          Also, I would suggest to use just the Selenium Grid 2 jar in the plugin as a dependency, and do not do any changes to the Selenium itself, in order to make the Selenium upgrades easier...

          Now it should be easier, because all modules of Selenium Grid 2 (hub, rc, webrdive) are integrated in a single selenium-server-standalone-2...jar

          Show
          salmira Tetiana Tvardovska added a comment - Totally agree that the plugin need to be updated to Selenium Grid 2.0. Such update would be more usefull. Also, I would suggest to use just the Selenium Grid 2 jar in the plugin as a dependency, and do not do any changes to the Selenium itself, in order to make the Selenium upgrades easier... Now it should be easier, because all modules of Selenium Grid 2 (hub, rc, webrdive) are integrated in a single selenium-server-standalone-2...jar
          Hide
          mawatech Markus Wagner added a comment -

          Is there an estimated date when the selenium grid plugin gets updated to selenium 2 (webdriver)?

          Show
          mawatech Markus Wagner added a comment - Is there an estimated date when the selenium grid plugin gets updated to selenium 2 (webdriver)?
          Hide
          darkrift Richard Lavoie added a comment -

          selenium plugin v2.0 was released last December (December 26th 2011), and should be able to handle FF up to 8 or even 9. Can you try that version and see if that solves your issue an update this ticket accordingly if so ?

          Show
          darkrift Richard Lavoie added a comment - selenium plugin v2.0 was released last December (December 26th 2011), and should be able to handle FF up to 8 or even 9. Can you try that version and see if that solves your issue an update this ticket accordingly if so ?
          Hide
          darkrift Richard Lavoie added a comment -

          The latest plugin also support WebDriver (grid v2)

          Show
          darkrift Richard Lavoie added a comment - The latest plugin also support WebDriver (grid v2)
          Hide
          mbraun Martin Braun added a comment -

          Works beautifully for us after updating this plugin. Best christmas present ever

          Show
          mbraun Martin Braun added a comment - Works beautifully for us after updating this plugin. Best christmas present ever
          Hide
          desperado Ruslan Strazhnyk added a comment -

          Resolving this issue as fixed. However the plugin should always have updated selenium Grid2 version, would be great to provide a check and download the newest version and so there would be no need to update the plugin every time selenium server jar file gets updated officially.

          Show
          desperado Ruslan Strazhnyk added a comment - Resolving this issue as fixed. However the plugin should always have updated selenium Grid2 version, would be great to provide a check and download the newest version and so there would be no need to update the plugin every time selenium server jar file gets updated officially.
          Hide
          lagin Lubos Lagin added a comment -

          Is this issue solved? I would like to have always the newest version of Grid, that's not possible now, without rewriting old .jar file. But still, there are issues with it after I change that files.

          Show
          lagin Lubos Lagin added a comment - Is this issue solved? I would like to have always the newest version of Grid, that's not possible now, without rewriting old .jar file. But still, there are issues with it after I change that files.
          Hide
          apgray apgray added a comment -

          Agree that it should be always updated.

          I have an issue now that Selenium Grid does not work with Firefox 13.0.1

          I have raised ticket JENKINS-14207 requesting update and assigned to Kohsuke. Please vote for this

          Show
          apgray apgray added a comment - Agree that it should be always updated. I have an issue now that Selenium Grid does not work with Firefox 13.0.1 I have raised ticket JENKINS-14207 requesting update and assigned to Kohsuke. Please vote for this
          Hide
          apgray apgray added a comment -

          Failing on Firefox 13.0.1. Please also see defect JENKINS-14207

          Show
          apgray apgray added a comment - Failing on Firefox 13.0.1. Please also see defect JENKINS-14207
          Hide
          darkrift Richard Lavoie added a comment -

          There is one major problem with automagic update anyway.

          The selenium process is started when jenkins starts (on the master) and when a slave starts. To keep the process up to date, you'd have to restart jenkins everytime you update anyway. If you don't restart and only update the jar file, there are some risks that some already loaded classes throws exception because of the class definition is different from the other version.

          That is less of a problem for slaves, but for the master node, I doubt this is resolvable without a restart.

          Ideas ?

          Show
          darkrift Richard Lavoie added a comment - There is one major problem with automagic update anyway. The selenium process is started when jenkins starts (on the master) and when a slave starts. To keep the process up to date, you'd have to restart jenkins everytime you update anyway. If you don't restart and only update the jar file, there are some risks that some already loaded classes throws exception because of the class definition is different from the other version. That is less of a problem for slaves, but for the master node, I doubt this is resolvable without a restart. Ideas ?
          Hide
          salmira Tetiana Tvardovska added a comment -

          I do not see any problem in restarting Jenkins when Selenium Grid is updated.
          I restart it in an plugin update, so it is a normal workflow for any Jenkins update...

          It would be fine if Selenium Grid upgrade needs just a Jenkins restart after user confirmation

          Show
          salmira Tetiana Tvardovska added a comment - I do not see any problem in restarting Jenkins when Selenium Grid is updated. I restart it in an plugin update, so it is a normal workflow for any Jenkins update... It would be fine if Selenium Grid upgrade needs just a Jenkins restart after user confirmation
          Hide
          darkrift Richard Lavoie added a comment - - edited

          Version 2.1 has selenium 2.25 included. It also has ALOT of new additions like per node configurations and multi instance running on the same child (runs all the maching configuration for that node)

          Show
          darkrift Richard Lavoie added a comment - - edited Version 2.1 has selenium 2.25 included. It also has ALOT of new additions like per node configurations and multi instance running on the same child (runs all the maching configuration for that node)

            People

            • Assignee:
              darkrift Richard Lavoie
              Reporter:
              salmira Tetiana Tvardovska
            • Votes:
              17 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

              • Created:
                Updated: