Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: chromedriver-plugin, selenium-plugin
-
Labels:None
-
Similar Issues:
Description
"Custom RC node configuration" in Selenium plugin produces a config which lacks the essential JVM option - Chrome driver location, though it is supplied in the "Chrome binary path" field. Same config produced with "Custom web driver configuration" sets the JVM 'webdriver.chrome.driver' option, as could be seen from the attached screenshots.
Also 'browserName' settings have different names to those obtained through "Custom web driver configuration" (please refer to the screenshots again):
"Custom web driver config": browserNames - 'firefox', 'chrome'
"Custom RC node config": browserNames - '*firefox', '*googlechrome'
At the moment it prevents me from using the "Custom RC node config" which I need to use the '-log' and '-browserLog' options.
I think it would be also beneficial to merge those two different ways to configure Selenium server into one, by simply adding a 'JVM options' field to one of them.
Also logged a github issue here: https://github.com/jenkinsci/selenium-plugin/issues/37
The name with stars are from the old selenium RC and are valid, the binary path is a problem and will be fixed in the next release.