QA/Execution/Web Testing/Automation/Selenium Grid: Difference between revisions
< QA | Execution | Web Testing | Automation
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
=== Starting the Hub === | === Starting the Hub === | ||
* VNC into or use Screen, and go on qa-selenium.mv.mozilla.com, | * VNC into or use Screen, and go on qa-selenium.mv.mozilla.com, | ||
* start a screen session -> screen -S selenium_grid_hub | |||
* cd moz-grid-config | * cd moz-grid-config | ||
* | * start the hub -> ./launchHub.sh | ||
=== Starting RCs === | === Starting RCs === | ||
Revision as of 21:56, 27 April 2011
Startup
Starting the Hub
- VNC into or use Screen, and go on qa-selenium.mv.mozilla.com,
- start a screen session -> screen -S selenium_grid_hub
- cd moz-grid-config
- start the hub -> ./launchHub.sh
Starting RCs
Shutdown
Shutdown the Hub
Shutdown the RCs
Upgrading
Upgrading Jenkins
- Load http://qa-selenium.mv.mozilla.com:8080/
- Click on "Manage Jenkins" - http://qa-selenium.mv.mozilla.com:8080/manage
- Click on "Prepare for Shutdown" - http://qa-selenium.mv.mozilla.com:8080/quietDown
- VNC into qa-selenium.mv.mozilla.com and go to the Terminal window and CTRL+C (you'll see Java processes shutting down)
- Now, either arrow-up, or explicitly do java -jar jenkins.war -- this should restart Jenkins, and be it! It'll take some time for it to fully come back up, and for qatestbot to join #mozwebqa
Moz-Grid-Config
References
- Grid Admin Console
- Grid Hub Snapshot
- Github config snapshot