[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Richard Lavoie commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I'm trying to convert the tests to the new recipe and fixture and I'm having some problems with that. I'll also try to add more tests to this plugin as it's coverage is really suffering.. However, in a few days, maybe weeks I believe, this should be done. I'm mostly working on this part time outside of my job so I'm not able to put alot of time in this. I'm doing the best I can because I know I put this plugin aside for way too long before fixing this issue. I'll probably end up release this after manually validating it in a real installation so I can release it even if the tests and the coverage is not how I'd like it to be. Stay tuned ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Richard Lavoie commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. This should be fixed with commit 0b77252fc88ba9ac3ab2a7faf7b5a3a4da61bbc1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25987) Selenium Grid fails to start Selenium Server on slaves
Richard Lavoie resolved JENKINS-25987 as Duplicate Selenium Grid fails to start Selenium Server on slaves Duplicate of JENKINS-25583 Change By: Richard Lavoie (10/Dec/14 1:30 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25658) Selenium Node (Jenkins slave) doesn't start
Richard Lavoie resolved JENKINS-25658 as Fixed Selenium Node (Jenkins slave) doesnt start duplicate of JENKINS-25583 Change By: Richard Lavoie (10/Dec/14 1:31 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-18806) Selenium grid plugin have the error Subversion checkout has been canceled on the slave
Richard Lavoie commented on JENKINS-18806 Selenium grid plugin have the error Subversion checkout has been canceled on the slave Just how is this related to the selenium plugin ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Richard Lavoie commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. It seems that a new version of Jenkins has added a method call to Jenkins.getInstance() when create a new Channel (the trick I use to create multiple selenium slaves per node) which makes this error occur when the code is executed on the slave. When the code is executed on the slave, Jenkins.getInstance() returns null. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-15721) Cannot add browsers due to template include exception
Richard Lavoie resolved JENKINS-15721 as Fixed Cannot add browsers due to template include exception 2.4 has just been released and solves the issue Change By: Richard Lavoie (12/Apr/14 3:48 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-18638) Selenium Plugin New Configuration error: 'config.jelly' for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser
Richard Lavoie resolved JENKINS-18638 as Fixed Selenium Plugin New Configuration error: config.jelly for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser 2.4 has just been released and solves the issue Change By: Richard Lavoie (12/Apr/14 3:47 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-12805) Let Jenkins user to stop/start/restart Selenium grid server (hub)
Richard Lavoie resolved JENKINS-12805 as Fixed Let Jenkins user to stop/start/restart Selenium grid server (hub) Hub can be restarted now in 2.4 Change By: Richard Lavoie (12/Apr/14 3:50 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-12754) selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't
Richard Lavoie resolved JENKINS-12754 as Fixed selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesnt Works now when you specify the path to the chromedriver executable Change By: Richard Lavoie (12/Apr/14 3:51 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-22069) Client can not register to Selenium grid if jenkins is served via a proxy
Richard Lavoie resolved JENKINS-22069 as Fixed Client can not register to Selenium grid if jenkins is served via a proxy Version 2.4 now has a way to define which host you want the slaves to connect to. It can either be to use the default jenkins URL or another user defined static ip/host Change By: Richard Lavoie (12/Apr/14 3:52 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-18102) Grid Hub version needs to match latest version at Selenium HQ
Richard Lavoie resolved JENKINS-18102 as Fixed Grid Hub version needs to match latest version at Selenium HQ Version 2.4 has now 2.41.0 bundled in it along with IEServerDriver executables Change By: Richard Lavoie (12/Apr/14 3:54 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-12675) Add an option to install specific selenium version on the running nodes
Richard Lavoie resolved JENKINS-12675 as Fixed Add an option to install specific selenium version on the running nodes Change By: Richard Lavoie (12/Apr/14 3:55 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [selenium] (JENKINS-12675) Add an option to install specific selenium version on the running nodes
Richard Lavoie commented on JENKINS-12675 Add an option to install specific selenium version on the running nodes It is unfortunately not that easy because when new versions of selenium gets out, sometimes it comes with new servers binaries (IE driver server) which is hard to decouple from the main plugin. Version 2.4 has been released today and includes 2.41.0 which was just released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chromedriver] (JENKINS-21473) Selenium plugin Custom RC node configuration produces config lacking JVM options and starred browser names
Richard Lavoie resolved JENKINS-21473 as Fixed Selenium plugin Custom RC node configuration produces config lacking JVM options and starred browser names Binary path should be solved in 2.4 which was just released. Change By: Richard Lavoie (12/Apr/14 3:58 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chromedriver] (JENKINS-21473) Selenium plugin Custom RC node configuration produces config lacking JVM options and starred browser names
Richard Lavoie commented on JENKINS-21473 Selenium plugin Custom RC node configuration produces config lacking JVM options and starred browser names The name with stars are from the old selenium RC and are valid, the binary path is a problem and will be fixed in the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16017) Workspace will not create in Jenkins from script
Richard Lavoie updated JENKINS-16017 Workspace will not create in Jenkins from script That is not related to selenium plugin Change By: Richard Lavoie (14/Mar/14 11:54 PM) Assignee: RichardLavoie Component/s: core Component/s: selenium This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [seleniumhq] (JENKINS-11317) SeleniumReport struckedat--INFO - Checking Resource aliases
Richard Lavoie updated JENKINS-11317 SeleniumReport struckedat--INFO - Checking Resource aliases Wrong component Change By: Richard Lavoie (13/Mar/14 12:37 AM) Component/s: seleniumhq Component/s: selenium This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15284) Selenium hub doesn't work on a server with multiple interface
Richard Lavoie commented on JENKINS-15284 Selenium hub doesnt work on a server with multiple interface If your are using the default port, there is another process running on that port thus ehy you have a problem loading the hub. Can you try using another port for the hub and try again ? As far as I know, the -host should only bind it to o e interface while not specifying should listen on all. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15284) Selenium hub doesn't work on a server with multiple interface
Richard Lavoie commented on JENKINS-15284 Selenium hub doesnt work on a server with multiple interface what do you see when you check in the logs of jenkins ? any errors ? What's the output ewhen you do a "netstat -nlp" ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14404) Selenium Plugin won't compile
Richard Lavoie commented on JENKINS-14404 Selenium Plugin wont compile Can you update and see if it works now ? The maven repository should be the one from jenkins, not maven central so if you have overrides in your settings.xml, that also might be the issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid
Richard Lavoie commented on JENKINS-14856 Slave Registered Remote Controls not identified in Jenkins Selenium Grid Does that happen when using the latest 2.2 version ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid
Richard Lavoie assigned JENKINS-14856 to Richard Lavoie Slave Registered Remote Controls not identified in Jenkins Selenium Grid Change By: Richard Lavoie (08/Sep/12 1:48 PM) Assignee: KohsukeKawaguchi RichardLavoie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12842) Allow to pass proxy and other system properties to selenium grid
Richard Lavoie assigned JENKINS-12842 to Richard Lavoie Allow to pass proxy and other system properties to selenium grid Change By: Richard Lavoie (08/Sep/12 1:52 PM) Assignee: KohsukeKawaguchi RichardLavoie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10759) RC should try a fixed port first, and only fall back to random port if that doesn't work
Richard Lavoie commented on JENKINS-10759 RC should try a fixed port first, and only fall back to random port if that doesnt work With the latest plugin version (since 2.1), you can specify on which port the selenium node should listen for requests. Or are you taking about the high ports to make jenkins connect to childs with the remoting library (-connectTo parameter) ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9799) Let Jenkins start/stop X server with Selenium RC servers
Richard Lavoie assigned JENKINS-9799 to Richard Lavoie Let Jenkins start/stop X server with Selenium RC servers Change By: Richard Lavoie (08/Sep/12 2:02 PM) Assignee: KohsukeKawaguchi RichardLavoie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6661) Adding -singleWindow option to RC Grid conguration
Richard Lavoie assigned JENKINS-6661 to Richard Lavoie Adding -singleWindow option to RC Grid conguration Change By: Richard Lavoie (08/Sep/12 2:04 PM) Assignee: KohsukeKawaguchi RichardLavoie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8580) Upgrade Selenium Grid Plugin to Selenium Grid 2.0
Richard Lavoie commented on JENKINS-8580 Upgrade Selenium Grid Plugin to Selenium Grid 2.0 Version 2.2 has selenium 2.25 included. It also has ALOT of new additions like per node configurations and multi instance running on the same child (runs all the maching configuration for that node) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8580) Upgrade Selenium Grid Plugin to Selenium Grid 2.0
Richard Lavoie edited a comment on JENKINS-8580 Upgrade Selenium Grid Plugin to Selenium Grid 2.0 Version 2.1 has selenium 2.25 included. It also has ALOT of new additions like per node configurations and multi instance running on the same child (runs all the maching configuration for that node) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9285) I am unable to test the scripts through selenium
Richard Lavoie assigned JENKINS-9285 to Richard Lavoie I am unable to test the scripts through selenium Change By: Richard Lavoie (08/Sep/12 2:10 PM) Assignee: KohsukeKawaguchi RichardLavoie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14207) Upgrade Selenium Grid Plugin to latest Selenium
Richard Lavoie commented on JENKINS-14207 Upgrade Selenium Grid Plugin to latest Selenium Latest release (v2.1) has been updated to latest version of selenium (v2.25) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14207) Upgrade Selenium Grid Plugin to latest Selenium
Richard Lavoie resolved JENKINS-14207 as Fixed Upgrade Selenium Grid Plugin to latest Selenium Should be fixed with latest release of plugin Change By: Richard Lavoie (04/Sep/12 4:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6197) Failed Loading plugin selenium
Richard Lavoie assigned JENKINS-6197 to Richard Lavoie Failed Loading plugin selenium Change By: Richard Lavoie (04/Sep/12 4:16 AM) Assignee: KohsukeKawaguchi RichardLavoie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6197) Failed Loading plugin selenium
Richard Lavoie resolved JENKINS-6197 as Fixed Failed Loading plugin selenium Old post, should be fixed with latest release of plugin v2.1 and using a more recent jenkins version. Change By: Richard Lavoie (04/Sep/12 4:17 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5288) Environment variables are not set in slaves
Richard Lavoie commented on JENKINS-5288 Environment variables are not set in slaves The new version allows configurations to set the DISPLAY variable so it can be used with the XVFB plugin on headless servers as well as UI enabled servers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10206) Dynamically select nodes to run SeleniumServer on based on node label
Richard Lavoie resolved JENKINS-10206 as Fixed Dynamically select nodes to run SeleniumServer on based on node label This is the main new features of the latest (v2.1) selenium plugin version Change By: Richard Lavoie (04/Sep/12 4:21 AM) Status: Open Resolved Assignee: KohsukeKawaguchi RichardLavoie Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11743) selenium plugin -- slaves/remote control servers stay in in use status even they are not really in use
Richard Lavoie resolved JENKINS-11743 as Fixed selenium plugin -- slaves/remote control servers stay in in use status even they are not really in use Should not happen anymore with the timeout option from selenium grid. Latest version v2.1 now includes selenium 2.25 which would take care of the timeout of the sessions. Change By: Richard Lavoie (04/Sep/12 4:26 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12754) selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't
[ https://issues.jenkins-ci.org/browse/JENKINS-12754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Lavoie reassigned JENKINS-12754: Assignee: Richard Lavoie (was: Kohsuke Kawaguchi) selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't Key: JENKINS-12754 URL: https://issues.jenkins-ci.org/browse/JENKINS-12754 Project: Jenkins Issue Type: Bug Components: selenium Affects Versions: current Environment: ubuntu 1004... Reporter: Michael Higgins Assignee: Richard Lavoie Labels: plugin This code, driver = Selenium::WebDriver.for(:remote, :url = 'http://slave-tb2.puppetlabs.lan:/wd/hub/', :desired_capabilities = :chrome) Should work to start a webdriver session with chrome... but doesn't. Works as Jenkins user from jenkins. However, driver = Selenium::WebDriver.for :chrome ... works just fine. I raise this because it works as it should with :remote :firefox. -- 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
[JIRA] (JENKINS-12675) Add an option to install specific selenium version on the running nodes
[ https://issues.jenkins-ci.org/browse/JENKINS-12675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Lavoie reassigned JENKINS-12675: Assignee: Richard Lavoie (was: Kohsuke Kawaguchi) Add an option to install specific selenium version on the running nodes --- Key: JENKINS-12675 URL: https://issues.jenkins-ci.org/browse/JENKINS-12675 Project: Jenkins Issue Type: New Feature Components: selenium Reporter: Richard Lavoie Assignee: Richard Lavoie Priority: Minor People have been asking over email that it would be nice to be able to use the latest selenium version, so here is the ticket for that. -- 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
[JIRA] (JENKINS-12463) Selenium grid v2 could have different configuration per slave
[ https://issues.jenkins-ci.org/browse/JENKINS-12463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158775#comment-158775 ] Richard Lavoie commented on JENKINS-12463: -- Thanks for the feedback. Here is some precision about how these needs. Since I don't want to clutter the configuration UI, some configurations will only be available through the FileConfiguration, I'm talking about d and e here. This is some pretty advanced config which I doubt will be frequently used in jenkins. A, B and C are going to be taken care of (b is done, a was not in my mind but easy to do, and e only needs to specify the path for chromedriver which is easy as well) F is behing handled by another issue, see https://issues.jenkins-ci.org/browse/JENKINS-12675 If you want to check the code I've done so far, you can take it from : https://github.com/darkrift/selenium-plugin I'm fairly new to jenkins dev as well, started doing those changes 2 weeks ago but it's rather easy once you know the available parts in jenkins. If you have anything else you want, please submit them. Richard 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
[JIRA] (JENKINS-12463) Selenium grid v2 could have different configuration per slave
[ https://issues.jenkins-ci.org/browse/JENKINS-12463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158776#comment-158776 ] Richard Lavoie commented on JENKINS-12463: -- Can you just explain the goal of D ? Since the hub is running in jenkins directly, I don't see how this could be useful for one to specify it's servlets. Thinking about it, I even doubt it will work to add the custom jar to allow that just like you don't have the flexibility to specify your own CapabilityMatcher because it's jenkins that handles that ... Maybe that needs to be thought about, but I don't see the use rather than using an independant grid for more complex configurations/specifications. What's your thoughts about it ? Thanks Richard 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
[JIRA] (JENKINS-12463) Selenium grid v2 could have different configuration per slave
[ https://issues.jenkins-ci.org/browse/JENKINS-12463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Lavoie reassigned JENKINS-12463: Assignee: Richard Lavoie (was: Kohsuke Kawaguchi) 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: Richard Lavoie 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
[JIRA] (JENKINS-11743) selenium plugin -- slaves/remote control servers stay in in use status even they are not really in use
[ https://issues.jenkins-ci.org/browse/JENKINS-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158799#comment-158799 ] Richard Lavoie commented on JENKINS-11743: -- The problem is not solely related to the jenkins plugin. If your tests don't close/quit the browser at the end, selenium nodes think they are still having a session which is what jenkins plugin uses to validate if it's in use. Thankfully, there is actually a way to tell the nodes to close the browsers when they didn't receive a command after a while thus closing dangling sessions/browsers. The current plugin doesn't support that option yet (-timeout) but there is an an opened issue I'm currently working on to improve node configurations which will include that option. See https://issues.jenkins-ci.org/browse/JENKINS-12463 selenium plugin -- slaves/remote control servers stay in in use status even they are not really in use -- Key: JENKINS-11743 URL: https://issues.jenkins-ci.org/browse/JENKINS-11743 Project: Jenkins Issue Type: Bug Components: selenium Affects Versions: current Environment: jenkins 1.437 selenium plugin 1.4 OS: CentOS release 5.7 (Final) Reporter: hinling yeung Assignee: Kohsuke Kawaguchi I have been running into this problem ever since I switched to use the jenkins selenium plugin as my grid. After the grid has been running for a while, the slaves/rc servers which are connected to the grid start to appear as in use. When I logged on to the rc servers to check whether they are actually in use, they were actually idle with the browser windows still open but not doing anything. I checked the RC log and it usually stuck at Slave successfully connected: JNLP agent connected from /10.1.104.72 ===[JENKINS REMOTING CAPACITY]===Slave.jar version: 2.11 This is a Windows slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online When this happens, it happens to all the RCs. I have to restart the jenkins server to get out of this in use state. -- 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
[JIRA] (JENKINS-11743) selenium plugin -- slaves/remote control servers stay in in use status even they are not really in use
[ https://issues.jenkins-ci.org/browse/JENKINS-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Lavoie reassigned JENKINS-11743: Assignee: Richard Lavoie (was: Kohsuke Kawaguchi) selenium plugin -- slaves/remote control servers stay in in use status even they are not really in use -- Key: JENKINS-11743 URL: https://issues.jenkins-ci.org/browse/JENKINS-11743 Project: Jenkins Issue Type: Bug Components: selenium Affects Versions: current Environment: jenkins 1.437 selenium plugin 1.4 OS: CentOS release 5.7 (Final) Reporter: hinling yeung Assignee: Richard Lavoie I have been running into this problem ever since I switched to use the jenkins selenium plugin as my grid. After the grid has been running for a while, the slaves/rc servers which are connected to the grid start to appear as in use. When I logged on to the rc servers to check whether they are actually in use, they were actually idle with the browser windows still open but not doing anything. I checked the RC log and it usually stuck at Slave successfully connected: JNLP agent connected from /10.1.104.72 ===[JENKINS REMOTING CAPACITY]===Slave.jar version: 2.11 This is a Windows slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Slave successfully connected and online When this happens, it happens to all the RCs. I have to restart the jenkins server to get out of this in use state. -- 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
[JIRA] (JENKINS-12456) Automatic deploy script should be deployed only on machines with specific labels
[ https://issues.jenkins-ci.org/browse/JENKINS-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Lavoie updated JENKINS-12456: - Description: Plugin that deploys itself automatically on slaves should only deploy if the slave has some specific labels. The use case here is that not all our slaves might be related to the plugin it wants to be installed on. The labels could start with jenkins-plugin- so we know it's for a jenkins plugin and it could add the plugin name after that prefix so we know which plugin it is. This can be applied to hadoop as well as ChromeDriver unless it uses the configuration of selenium grid v2 exclude pattern configuration which is not the case in the trunk. Unless this feature can be controlled somewhere that I've not seen, this is pretty bad to install some stuff on machines that don't need it or will fail to work because the distant machine is not compatible with the plugin was: Plugin that deploys itself automatically on slaves should only deploy if the slave has some specific labels. The use case here is that not all our slaves might be related to the plugin it wants to be installed on. The labels could start with jenkins-plugin- so we know it's for a jenkins plugin and it could add the plugin name after that prefix so we know which plugin it is. This can be applied to hadoop as well as ChromeDriver unless it uses the configuration of selenium grid v2 exclude pattern configuration which is not the case in the trunk. Unless this feature can be controlled somewhere that I've not seen, this is pretty bad to install some stuff on machines that don't need it or will fail to work because the distant machine is not compatible with the plugin (ChromeDriver is useless on a unix non-gui slave) Automatic deploy script should be deployed only on machines with specific labels Key: JENKINS-12456 URL: https://issues.jenkins-ci.org/browse/JENKINS-12456 Project: Jenkins Issue Type: Improvement Components: plugin Environment: linux ubuntu, Jenkins 1.448 Reporter: Richard Lavoie Labels: ChromeDriver, Selenium, hadoop Plugin that deploys itself automatically on slaves should only deploy if the slave has some specific labels. The use case here is that not all our slaves might be related to the plugin it wants to be installed on. The labels could start with jenkins-plugin- so we know it's for a jenkins plugin and it could add the plugin name after that prefix so we know which plugin it is. This can be applied to hadoop as well as ChromeDriver unless it uses the configuration of selenium grid v2 exclude pattern configuration which is not the case in the trunk. Unless this feature can be controlled somewhere that I've not seen, this is pretty bad to install some stuff on machines that don't need it or will fail to work because the distant machine is not compatible with the plugin -- 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
