TestEngineering/Web/Automation/Credentials: Difference between revisions

m
StuartPhilp moved page QA/Execution/Web Testing/Automation/Credentials to TestEngineering/Web/Automation/Credentials: reorganizing wiki under Test Engineering
(Added link to deploy key help text)
m (StuartPhilp moved page QA/Execution/Web Testing/Automation/Credentials to TestEngineering/Web/Automation/Credentials: reorganizing wiki under Test Engineering)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
= WebQA Credentials =
[[File:Configfileproviderjobexample.png|framed|Example job configured to use a credentials file]]We are using the [https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin Config File Provider plugin] for Jenkins to provide credentials to jobs. These files can be accessed via the [https://webqa-ci.mozilla.com/configfiles/ Config File Management] page. Access is restricted to Jenkins administrators. To use a credendials file in a job, check the '''Provide Configuration files''' box under '''Build Environment''' and pick the file you need.
 
We are using a [https://github.com/mozilla/webqa-credentials private GitHub repository] to store credentials for WebQA projects. These credentials can be used by automation projects.
 
To read/write to this repository you must first have access to it. The CI server (qa-selenium.mv.mozilla.com) has a [https://help.github.com/articles/managing-deploy-keys deploy key] configured so it can pull updates for the automated tests. The repository is currently checked out to <tt>/Users/webqa/webqa-credentials</tt>, and can be updated using the command <tt>git pull</tt>.
 
The first automated project to use this was [https://github.com/mozilla/Addon-Tests AMO], where the credentials are stored in a simple [http://www.yaml.org/ YAML] format. The credentials file is then passed to the tests on the command line by specifying <tt>--credentialsfile=<file></tt>. This means that we keep our passwords secure, and allow anyone running the tests locally to use the provided <tt>credentials.yaml</tt> template to provide their own login details.
81

edits