If you have any suggestions on how to improve the understanding of the plugin form elements, I'm all hears.
On Wed, Oct 10, 2012 at 6:51 PM, Richard Lavoie <[email protected]>wrote: > Comments inlined. > > On Wed, Oct 10, 2012 at 4:22 PM, Jeff <[email protected]> wrote: > >> I'm missing something simple and the documentation for the Selenium Grid >> Plugin doesn't cover these in any detail. I'm using the latest Selenium >> Plugin with Jenkins v1.482. >> >> *First:* >> >> I can't get the plugin to find my JSON file that I'm trying to use to >> configure the node. I've tried the following: >> >> C:\.jenkins\SeleniumNodeConfig\nodecfg.json >> C:/.jenkins/SeleniumNodeConfig/nodecfg.json >> C:\\.jenkins\\SeleniumNodeConfig\\nodecfg.json >> file:///C:/.jenkins/SeleniumNodeConfig/nodecfg.json >> file:////.jenkins/SeleniumNodeConfig/nodecfg.json >> C:/Temp/nodecfg.json >> file:///C:/Temp/nodecfg.json >> >> > > did you try file:/c:/Temp/nodecfg.json ? > > > I'll try to look into it tonight to at least add some examples. I thought > people would prefer using the HTTP scheme than local files for distributed > environment. > > >> But Jenkins throws a NullPointerException during startup in each case: >> >> java.lang.NullPointerException >> at >> hudson.plugins.selenium.PluginImpl.getGlobalConfigurationForComputer(PluginImpl.java:598) >> at >> hudson.plugins.selenium.PluginImpl.startSeleniumNode(PluginImpl.java:505) >> at >> hudson.plugins.selenium.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:26) >> at jenkins.model.Jenkins.<init>(Jenkins.java:832) >> at hudson.model.Hudson.<init>(Hudson.java:81) >> at hudson.model.Hudson.<init>(Hudson.java:77) >> at hudson.WebAppMain$2.run(WebAppMain.java:214) >> >> What am I missing? >> >> >> >> *Second:* >> >> Can anyone explain the "Matching type" setting in the node configuration >> editor? I am not grasping what it is "matching" to? I thought that the >> configuration is defining the node itself so how or what is it matching to? >> >> >> > The concept of configurations in this plugin is global to all nodes. It > will try to apply all the "matching" configurations to every nodes it can > work on. So when a node comes online, for each configurations defined, it > will ask the matcher if this configuration is allowed on this node. There > are currently 3 matchers, All (will run this configuration on all the > nodes), None (will run it on no nodes, hence disable a configuration) and > label matching where the configuration will run on this node only if this > computer label matches the specified label expression. > > There is a distinction to make in between a selenium node (a running java > process on the machine) and the jenkins computer node (the machine > slave/master that will host the selenium java process) > > While this plugin creates selenium node configurations, the selenium > configurations are applied to jenkins computer nodes. > > Hope that clarifies it. > > > Thanks! >> >> -- >> Jeff Vincent >> [email protected] >> See my LinkedIn profile at: >> http://www.linkedin.com/in/rjeffreyvincent >> I ♥ DropBox <http://db.tt/9O6LfBX> !! >> >> > > > -- > Richard Lavoie > IT consultant / consultant en informatique > -- Richard Lavoie IT consultant / consultant en informatique
