Wikimedia Release Engineering Team

This is the team responsible for Release Engineering/Management and QA at the Wikimedia Foundation. We predominately use the QA mailing list along with conversations on the appropriate IRC channels (especially, , , and ).

= Status =

= Quarterly Reviews =
 * April 2014
 * February 2014
 * November 2013
 * August 2013

= Wishlist =

We maintain a list of projects that would be great to have done, but are not on our roadmap in in the near term. See the wishlist here.

= Meetings =

See /Meetings for notes from the Showcase meetings of the Release and QA Team.

= April - July '14 Goals Progress = For past quarter's checkins, see the archives. See the WMF Engineering 13-14 goals page for the yearly view.

Deployment tooling

 * - Process through all (useful) pain points from the Dev/Deploy review session - (Greg)
 * - Integrate HHVM support into our deployment systems - (Bryan, Greg, ytbh RelEngineer, others from Platform)
 * - start the scap(py) & trebuchet integration conversation (stretch goal)

Beta cluster

 * - Support HHVM deployment tooling and puppet configuration testing - (Bryan, Antoine, ytbh RelEngineer)
 * - Swift cluster in beta (stretch goal)

MediaWiki Release

 * - Successfully support the release of MediaWiki 1.23 - (Antoine, Greg)
 * - Kickoff/complete second RFP - (Greg)
 * - Investigate and create useful release/deployment metrics visualizations - (Greg)

Browser tests

 * - Use tags to run builds appropriate to released versions (e.g. don't run master build on test2wiki) - (Chris)
 * - Retire Cloudbees Jenkins instance - (Željko)
 * - Integrate WMF Jenkins with new WMF SauceLabs account - (Željko, Antoine, Chris)
 * - Use API to create test data at runtime more widely (not just for MobileFrontend but also VisualEditor, Flow, local dev env etc.) - (Chris, Željko) Calling this done for the quarter, but we'll always be using it into the future
 * Used by MobileFrontend
 * Used by VisualEditor
 * Used by smoke tests (part of quarterly goals)
 * - Add browsertests to new repos e.g. GettingStarted - (Chris, Željko)

Hiring

 * - Complete hiring and train new Release Engineer (Greg, all)
 * - Complete hiring and train new Automation Engineer (Ruby)  (Chris, all)

Quarterly Review Action items

 * - create a plan for browser testing of MediaWiki 1.23 - Chris M
 * - Greg get firm requirements from Antoine, circle back to Mark who'll have an idea of Op's timelime for production Shinken.
 * - Figure out how to keep HHVM unit tests from delaying +2 for standard production commits (Antoine, Chris M, Zeljko)

Greg

 * - Process through pain points
 * - WMF product should be consulted on some shellbugs
 * - Successfully support the release of MediaWiki 1.23
 * - Kickoff/complete second RFP
 * - Refine Deployment_tooling/Notes/Deployment_system_requirements with Bryan
 * - Investigate and create useful release/deployment metrics visualizations

Antoine

 * - Support HHVM deployment tooling and puppet configuration testing
 * - Integrate WMF Jenkins with new WMF SauceLabs account
 * - RFC for Jenkins tests isolation
 * agreement by End of June
 * POC by End of July
 * - RFC for cross repositories testing and integration job in gate
 * - implementing cross repository cloner (aka have repositories match branches/zuul ref)

Mukunda

 * - read all the things
 * - WMF SUL/OAuth support T40
 * - security component support in Phab Upstream T4893, our phab T95
 * local 6 line hack
 * pinging evan regularly on real long term fix
 * - puppet wmflib beginnings

Bryan

 * Scap refactor/python port
 * ✅ Setup test environment in beta
 * Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link
 * ✅ Build JSON git info caches during scap
 * ✅ support in GitInfo.php
 * Code is deployed in beta (and prod) but it doesn't work as expected. See notes on bug for where I'm stuck.
 * - Integrate HHVM support into our deployment systems
 * Next generation deployment tooling
 * Support train deploys
 * ✅ Created Train deploy instructions on wikitech based on noted from Sam and experience in March

Chris

 * - migrate to WMF Jenkins
 * - create a plan for browser testing of MediaWiki 1.23
 * See https://gerrit.wikimedia.org/r/#/c/133507/
 * Chris Steipp had suggestions in email for further tests that map to legacy tests in /qa/browsertests repo
 * After discussion with Rob Lanphier, will port appropriate tests from /qa/browsertests to /mediawiki/core with Dan Duvall over time
 * - Use tags to run builds appropriate to released versions (e.g. don't run master build on test2wiki)
 * Antoine fleshing out a start of this idea at Zurich
 * - Use API to create test data at runtime more widely (not just for MobileFrontend but also VisualEditor, Flow, local dev env etc.)
 * Done for Mobile
 * Done for VisualEditor
 * Done for browser smoke tests
 * - hire new QA Tester

Dan

 * Read all the things
 * - VE broswer tests in Vagrant

Greg

 * - Process through pain points
 * - config changes not being deployed after merge (RT ticket filed], successfully in Ops' court)
 * - WMF product should be consulted on some shellbugs
 * email sent to WMF Product on 5/15
 * - onboard new Release Engineer
 * ongoing
 * - Successfully support the release of MediaWiki 1.23
 * - Kickoff/complete second RFP
 * - Refine Deployment_tooling/Notes/Deployment_system_requirements with Bryan
 * - Investigate and create useful release/deployment metrics visualizations

Antoine

 * - Figure out how to keep HHVM unit tests from delaying +2 for standard production commits
 * - Support HHVM deployment tooling and puppet configuration testing
 * - Integrate WMF Jenkins with new WMF SauceLabs account
 * - RFC for Jenkins tests isolation
 * - RFC for cross repositories testing and integration job in gate
 * - RFC for cross repositories testing and integration job in gate

Mukunda

 * - read all the things
 * - WMF SUL/OAuth support T40
 * - security component support in Phab Upstream T4893, our phab T95

Bryan

 * Scap refactor/python port
 * ✅ Setup test environment in beta
 * Repository .git is synchronised fine, but is broken for submodules because of hardcoded gitdir link
 * ✅ Build JSON git info caches during scap
 * ✅ support in GitInfo.php
 * Code is deployed in beta (and prod) but it doesn't work as expected. See notes on bug for where I'm stuck.
 * ✅ Use trebuchet to deploy scap scripts
 * Add scap/scap trebuchet target
 * Provision scap scripts using trebuchet
 * ✅ source organization cleanup
 * ✅ Change default console logging verbosity (less noise for deployers)
 * ✅ Convert sync-* to python
 * Extract common base class for sync operations
 * Convert sync-dir and sync-file to python
 * Convert sync-dblist to python
 * Convert sync-docroot to python
 * - Integrate HHVM support into our deployment systems
 * Next generation deployment tooling
 * Support train deploys
 * ✅ Created Train deploy instructions on wikitech based on noted from Sam and experience in March

Chris

 * - create a plan for browser testing of MediaWiki 1.23
 * See https://gerrit.wikimedia.org/r/#/c/133507/
 * Chris Steipp had suggestions in email for further tests that map to legacy tests in /qa/browsertests repo
 * After discussion with Rob Lanphier, will port appropriate tests from /qa/browsertests to /mediawiki/core with Dan Duvall over time
 * - Use tags to run builds appropriate to released versions (e.g. don't run master build on test2wiki)
 * Antoine fleshing out a start of this idea at Zurich
 * - Use API to create test data at runtime more widely (not just for MobileFrontend but also VisualEditor, Flow, local dev env etc.)
 * Done for Mobile
 * Done for VisualEditor
 * Done for browser smoke tests
 * - hire new QA Tester

Dan

 * Read all the things