Confirmed users
2,177
edits
Line 122: | Line 122: | ||
=== Update staging instance === | === Update staging instance === | ||
# If you're not on a Mozilla office network, connect to the [https://mana.mozilla.org/wiki/display/SD/VPN Mozilla VPN] | |||
# [http://webqa-ci-staging1.qa.scl3.mozilla.com:8080/login Login to Jenkins] | |||
# [http://webqa-ci-staging1.qa.scl3.mozilla.com:8080/quietDown Prepare Jenkins for shutdown] | |||
# Wait until no jobs are running | |||
# Connect to selenium-staging1.qa.scl3.mozilla.com using RDP | |||
# Stop the Selenium node by hitting Ctrl+C in the terminal window | |||
# Update the Selenium major and minor versions in <code>C:\Users\mozauto\moz-grid-config\default.properties</code> | |||
# Start the Selenium server by running <code>ant -autoproxy -Denv=staging -Dnode.host=IP</code> | |||
# Connect to selenium-5.qa.mtv2.mozilla.com using VNC | |||
# Stop the Selenium node by hitting Ctrl+C in the terminal window | |||
# Update the Selenium version in /Users/webqa/moz-grid-config/default.properties | |||
# Start the Selenium server by running <code>ant -Denv=staging</code> | |||
# Connect to selenium-hub-staging1.qa.scl3.mozilla.com using SSH | |||
# Stop the Selenium hub by running <code>sudo initctl stop selenium</code> | |||
# Update the Selenium version in <code>/etc/init/selenium.conf</code> | |||
# Start the Selenium hub by running <code>sudo initctl start selenium</code> | |||
# [http://webqa-ci-staging1.qa.scl3.mozilla.com:8080/cancelQuietDown Cancel the Jenkins shutdown] | |||
# Verify the hub and node versions on the [http://selenium-hub1.qa.scl3.mozilla.com:4444/grid/console Selenium hub console] | |||
=== | === Test staging instance === | ||
Run tests against the staging instance. You can do this locally by pointing your tests at host selenium-hub1.qa.scl3.mozilla.com and port 4444, or you can run tests via the [http://webqa-ci-staging1.qa.scl3.mozilla.com:8080/ staging Jenkins instance]. For convenience, there is a job named <code>grid.sanity</code> that will run a variety of tests against both the Windows and OS X platforms. | |||
=== Update moz-grid-config === | === Update moz-grid-config === | ||
Once testing is finished and we're satisfied that there are no regressions, submit a pull request for [https://github.com/mozilla/moz-grid-config moz-grid-config] that changes the version number in <code>default.properties</code>. This will need a review from a team member before it gets merged. It's good practice to then reset moz-grid-config on the staging nodes and pull in the official change. | |||
=== Update production instance === | === Update production instance === | ||
# [https://webqa-ci.mozilla.com/login Login to Jenkins] | |||
# [https://webqa-ci.mozilla.com/quietDown Prepare Jenkins for shutdown | |||
# Wait until no jobs are running | |||
# Connect to selenium1.qa.scl3.mozilla.com using RDP | |||
# Stop the Selenium node by hitting Ctrl+C in the terminal window | |||
# Pull down the latest moz-grid-config changes by running <code>git pull</code> | |||
# Start the Selenium server by running <code>ant -autoproxy -Denv=production</code> | |||
# Repeat steps 4-7 on selenium2, selenium3, selenium4, selenium5, and selenium6 | |||
# Connect to selenium.qa.mtv2.mozilla.com using VNC | |||
# Stop the Selenium node by hitting Ctrl+C in the terminal window | |||
# Pull down the latest moz-grid-config changes by running <code>git pull</code> | |||
# Start the Selenium server by running <code>ant -Denv=production</code> | |||
# Repeat steps 9-12 on selenium-7 | |||
# Connect to selenium-hub1.qa.scl3.mozilla.com using SSH | |||
# Stop the Selenium hub by running <code>sudo initctl stop selenium</code> | |||
# Update the Selenium version in /etc/init/selenium.conf | |||
# Start the Selenium hub by running <code>sudo initctl start selenium</code> | |||
# [https://webqa-ci.mozilla.com/cancelQuietDown Cancel the Jenkins shutdown] | |||
# Verify the hub and node versions on the [http://selenium-hub1.qa.scl3.mozilla.com:4444/grid/console Selenium hub console] |