Hi, The selenium plugin was never meant to make a build run on a particular node depending on browser capabilities.
What this plugin does is use your slaves as "browser providers" so that you can reuse your "sleeping" nodes. For example, let's say I have 2 nodes with matching selenium configurations, A and B, A being a windows machine that has IE and B an ubuntu desktop machine with Firefox. You launch a build and it goes on machine A. As part of your test, you need to test some code on IE. You create a new remote driver object, connecting to jenkins hub and requesting an IE session. Lucky you it's the same machine you are currently building on. IE gets started on machine A and you interact with it fir the said test. Now in another test you need to perform code in Firefox. You create a remote webdriver object, connecting to jenkins hub and request a firefox object. The browser is now launched on machine B but your build is still running on machine A. The node where your build runs is independant of the test session you will need in your tests. To make your "build" run on a given node, you need to use other mechanism (like labels for instance) because the selenium plugin only use slaves as "browser providers". It is not a "build redirector" that makes projects needing selenium run on hosts that has selenium matching configurations. Now if you have free nodes and the build doesn't want to run on them, the problem is elsewhere than in the selenium plugin. If jenkins itself isn't connected to the slave normally, there is something definitely wrong. The fact that the node is connected to the hub jenkins is hosting is also independant of jenkins being directly connected to this slave and be able to send jobs to it. Richard Lavoie > On 2015-09-16, at 03:58, steliosP <stellar...@gmail.com> wrote: > > Hello Richard. > The nodes are connected to jenkins hub, and are you can see them in selenium > grid hub management tab. > But my question remains: how you can build a project in jenkins, and make it > run on nodes?When upon pressing build you get :(pending—Waiting for next > available executor) > > >> On Monday, June 8, 2015 at 11:28:28 PM UTC+3, DarkRift wrote: >> I don't know how you are trying to connect to the nodes, but the plugin only >> starts the hub and uses the salevss to start selenium slaves on to use the >> browser from the slaves. I doesn't start build on the right "nodes" >> according to selenium capabilities or suite files. >> >> What you would do is in your trst code, connect your remote drivers to the >> jenkins master address to delegate the browser calls to the right selenium >> capabilitu for each tests. >> >> Hope that helps, >> >> Richard Lavoie >> >>> On 2015-05-21, at 11:11, steliosP <stell...@gmail.com> wrote: >>> >>> Any Selenium Grid plugin users around? >>> >>>> On Monday, May 18, 2015 at 12:55:26 PM UTC+3, steliosP wrote: >>>> Hello guys, I am trying to set up Jenkins with selenium grid. >>>> I have downloaded selenium plugin, and when I start the nodes, I can see >>>> them in Jenkin's selenium grid tab. >>>> However, whenI try to build my project, nothing happens, because jenkins >>>> doesn't find any connected nodes.It's the same message when you're not >>>> running in grid, and no slaves are connected: >>>> #361 (pending—Waiting for next available executor) >>>> >>>> Some info regarding the project I am building: >>>> A maven project, that pulls the latest from git, and then a parametrized >>>> build happens, that has the parameter >>>> -Dsuite.Files=testSuite.xml >>>> >>>> so only a specific testSuite is going to run >>>> >>>> Any solution to my problem? >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to jenkinsci-use...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/345ae109-55d3-462a-b7ba-1cb581d4cf2b%40googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/c1d12a46-5d5e-4a85-89f3-ff32a56ffd80%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/E2820714-C451-4FE3-B333-738C65237B57%40gmail.com. For more options, visit https://groups.google.com/d/optout.
