Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
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
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
- is related to
-
JENKINS-6207 Upgrade Selenium Grid Plugin to Selenium Grid 1.0.5
-
- Closed
-
Activity
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 ?
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 ? 
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 
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 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)
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) 
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-14207requesting update and assigned to Kohsuke. Please vote for this