Home > jenkins, potd > Jenkins ChromeDriver plugin

Jenkins ChromeDriver plugin

December 28th, 2011

I released Jenkins ChromeDriver plugin that auto-installs chromedriver on all slaves. Here is why this is useful.

ChromeDriver is needed to run WebDriver-based tests with Chrome. Unfortunately this is a native program, so in a heterogenous Jenkins, you need to make sure you have the right binary available on each of the slaves. While that’s not hard, it’s awfully tedious. This plugin fixes that by automating it.

This plugin would be a nice companion to the recently upgraded Selenium Grid plugin that automatically runs Selenium Grid on top of your Jenkins slaves. When you combined, you just install two plugins to the Jenkins master, and without touching slaves at all, you got the whole cluster instantly ready for Selenium2 WebDriver testing. How is that?

jenkins, potd ,

  1. Skúli Arnlaugsson
    December 29th, 2011 at 02:09 | #1

    Wow, this is a really nice plugin. I look forward to trying it out!

  2. Vijay Singh
    January 25th, 2012 at 16:47 | #2

    I would like to install the plugin manually – where can I download a .hpi version of it?

  3. Vijay Singh
    January 30th, 2012 at 22:37 | #4

    Thanks Kohsuke!

  4. Vijay Singh
    January 30th, 2012 at 22:44 | #5

    I think this may be quicker though I posted the same question on the plugin page…

    Post installing the Selenium Grid 2.0 Plugin (Jenkins 1.449) all the Slaves went OFFLINE. I thought the Grid works on top of the master & slaves setup.

    Any help appreciated.

  5. Vijay Singh
    January 30th, 2012 at 23:12 | #6

    An update – I had the Chrome Driver plugin also installed, which I believe is causing the slaves to go offline. They came back online once I disabled the Chrome driver plugin.

  6. Anitha V
    March 27th, 2012 at 23:07 | #7

    I am using Hudson Distributed Builds and the slaves fail to launch the chrome (Failed to initialize connection error in chromedriver.log) – do u think this plugin will help solve that problem? also looks like this works only on Jenkins and not on Hudson – is that so?

  7. Jiří Skřivánek
    May 22nd, 2014 at 06:56 | #8

    I installed both ChromeDriver plugin and Selenium Grid plugin. The file chromedriver.exe is copied to windows slave but it is not clear to me how to tell my JUnit tests where it is. Should I set it to a property and propagate it somehow to tests?

  1. No trackbacks yet.