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

Upgrade Selenium Grid Plugin to Selenium Grid 2.0

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Component/s: selenium-plugin
    • Labels:
      None
    • Similar Issues:

      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

        Attachments

          Issue Links

            Activity

            Hide
            apgray Andrew Gray 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 Andrew Gray 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 Andrew Gray added a comment -

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

            Show
            apgray Andrew Gray 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:
                  Resolved: