[
https://issues.jenkins-ci.org/browse/JENKINS-12463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158759#comment-158759
]
Krishnan Mahadevan commented on JENKINS-12463:
----------------------------------------------
Richard,
Here are a few things that I would want to be able to do using the plug-in.
a. Customize the hub by passing in a configuration file (a yaml file so that
the grid works parsing it Selenium1 grid mode), or a JSON file (Selenium2 grid
mode)
b. Customize the node by passing in either a JSON configuration file (or) by
passing command line arguments as well.
c. A provision to specify the chromedriver binary where it exists, because when
a webdriver node is spawned, unless and until it is fed the chromedriver binary
path, chrome executions may not work.
d. The grid has the capability to accept servlets which can be injected into
it. So I would want a provision wherein I can provide a custom built jar that
can be accepted by the plug-in, added to the classpath and then it be injected
into the grid via the -servlets command arg.
e. The node has the capability to accept custom proxies (apart from the default
proxy). I would want a provision wherein I can provide this as well.
f. Currently the plug-in works on by depending on a specific version of the
selenium standalone jar. If there is a way to de-couple this plug-in and the
jar it works with, it would give me the flexibility of upgrading the selenium2
dependency based on the selenium release and not warrant an updating of the
plug-in.
I am pretty new to jenkins plug-in development and I have no clue as to how
things work in general. If you have some time to walk me through on some
basics, perhaps I can pitch in on this as well.
> Selenium grid v2 could have different configuration per slave
> -------------------------------------------------------------
>
> Key: JENKINS-12463
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12463
> Project: Jenkins
> Issue Type: Improvement
> Components: master-slave, selenium
> Reporter: Richard Lavoie
> Assignee: Kohsuke Kawaguchi
>
> When running slaves with the selenium grid v2 plugin, each slave could have
> different configuration (some not supporting IE on linux, or not chrome). The
> suggestion here is to be able to configure the grid v2 configuration per
> slave. Not only on the master.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
