On 29.01.2014, at 17:25, Tonni Tielens <[email protected]> wrote:
> A test that seems to connect to a machine running Selenium somewhere in the > buildserver's network. I have no experience with Selenium, but the line in the stack trace seems to indicate a failure in connecting to google.com. https://github.com/jenkinsci/selenium-plugin/blob/master/src/test/java/hudson/plugins/selenium/SeleniumTest.java#L78 > - Why is the plugin still on Selenium version 2.29, while the source code > links to version 2.35? Because no release of the plugin has been created since this commit: https://github.com/jenkinsci/selenium-plugin/commit/316eccdef608e855863cf04b1c240fa2c7b8b762 (You could always install a snapshot build manually though if you want that change) > - What do we have to do to get this plugin updated to version 2.38? > > I'd be most willing to help to solve this issue, but I'm unsure on how to do > so. Fork the plugin on Github, change the Selenium version (and fix anything else that might require fixing due to the version change), fix the test if necessary (test locally!), and open a pull request. Even if nobody bothers to merge your change, you'll get your PR built on Cloudbees' server (maybe the problem resolved itself), and after a week or two you can request commit access, merge it yourself (http://jenkins-ci.org/pull-request-greeting), and then release it. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
