User:Stephend

Road to Single (prod) Jenkins

Goals:

1. ease the pain and cognitive load of migrating (and using/configuring/troubleshooting, etc.) jobs to our new, combined-team, AWS-provisioned Jenkins server
2. speed up the process by standardizing on processes + configurations (as much as possible), and ensuring we have accurate and up-to-date documentation

1. Updated docs on, or linked to from, its Mana page, covering:
   1. making sure your SSH key is in cloudops-deployment repo
   2. proxy setup (FoxyProxy/built-in manager) - we'll graciously transplant from https://mana.mozilla.org/wiki/display/~rpappalardo@mozilla.com/FTE+Jenkins+Access
   3. how to connect to bastion host
2. For Web QA projects we're migrating over as stand-alone jobs/builds (i.e. not-yet hooked into Dev + Ops' build + deploy pipeline):
   1. have implemented Tox and a Jenkinsfile, in that order - tracked in our Automation Baseline page
3. Decommission the following hosts, along with any dependencies:
   1. https://webqa-ci.mozilla.com/
   2. http://webqa-ci-staging1.qa.scl3.mozilla.com:8080/
   3. https://mana.mozilla.org/wiki/display/QA/webqa-ci-staging-temp1.qa.scl3.mozilla.com http://webqa-ci-staging-temp1.qa.scl3.mozilla.com:8080/