QA/Execution/Web Testing/Automation/Selenium Grid: Difference between revisions

Jump to navigation Jump to search

QA/Execution/Web Testing/Automation/Selenium Grid (view source)

Revision as of 01:33, 31 July 2012

2,805 bytes removed ,  31 July 2012
Removed Jenkins section as it now has its own page.
(Removed Jenkins section as it now has its own page.)
Line 136: Line 136:
* <code>move %USERPROFILE%/firefox-14 "\Program Files\Mozilla Firefox 14"</code>
* <code>move %USERPROFILE%/firefox-14 "\Program Files\Mozilla Firefox 14"</code>
* <code>del %TMP%\firefox-14.0.1.en-US.win32.exe</code>
* <code>del %TMP%\firefox-14.0.1.en-US.win32.exe</code>
== Jenkins ==
=== Starting Jenkins ===
# VPN in via Mozilla-MV to '''qa-selenium.mv.mozilla.org'''
# Look for an existing Terminal/Console window with a Jenkins process
#* If there's one there, you should just be able to cursor-up and type Enter/Return to launch
#* If not, launch as follows:
    java -jar -Xms2g -Xmx2g -XX:MaxPermSize=512M -Xincgc ~/Desktop/jenkins.war
=== Upgrading Jenkins ===
# Open the [http://qa-selenium.mv.mozilla.com:8080/ Jenkins dashboard] (must be on VPN)
# Click on [http://qa-selenium.mv.mozilla.com:8080/manage Manage Jenkins]
# Click on [http://qa-selenium.mv.mozilla.com:8080/quietDown Prepare for Shutdown]
# VNC into '''qa-selenium.mv.mozilla.com''' and go to the Terminal window and CTRL+C (you'll see Java processes shutting down)
# [[#Starting Jenkins|Start Jenkins]]
=== Jenkins Backup ===
Web QA is using the thinBackup (https://wiki.jenkins-ci.org/display/JENKINS/thinBackup) plugin to perform scheduled (currently daily) backups of the Jenkins XML files that store the Jenkins system config, jobs, plugins installed.
ThinBackup saves the backup to FS2 in the folder /public/QA/WebQA/Jenkins/
There is an unscheduled backup of the Plugins in this folder too but be aware these plugins may be out of date.
=== Restoration procedure ===
While thinBackup does backup a list of plugins used it cannot install them while restoring the Jenkins config and jobs. It will restore all of the settings that were used by the plugin but until the plugin is installed they won't be visible or active.
The work around to this is to install them manually before performing the restore. If a plugin is no longer available or obsolete then its settings may be lost.
Steps to restore WebQA's Jenkins instance:
# On the new/recovered server install and start a clean Jenkins instance.
# Open up that Jenkins instance and install thinBackup
# On the thinBackup settings page set the Backup directory to point to the fs2 directory.
# From the FS2 directory open the backed up list of plugins installedPlugins.xml in a text editor.
# In Jenkins install each plugin listed in the XML file. The first string in the <entry> matches the plugin-id. The plugin-id is listed in the information matrix at the top of the plugin's homepage (eg https://wiki.jenkins-ci.org/display/JENKINS/thinBackup). Alternatively you can copy the plugin from the folder in the Jenkins backup directory however because this folder is only backed up manually the plugins may be out of date. You'll need to use your best judgement here.
# Go back to thinBackup settings page and perform the thinBackup restore procedure.
# Restart Jenkins.
# Check that the jobs have retained the plugin settings.
NB if job settings have been lost then the plugin may not have been installed or be a different version.


== Setting hostname on Mac OS X ==
== Setting hostname on Mac OS X ==
Davehunt
Confirmed users
2,177

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/456328"

Navigation menu