Wikimedia Release Engineering Team/Checkin archive/20180212



Vacations/Important dates[edit]
How to do it
  • Feb 2nd: Mukunda vacation day
  • Feb 19 (Mon): President's Day (All US Staff)
  • Mar 30 (Fri): WMF Holiday
  • April 2: Željko (Holidays in Croatia - Easter Monday)
  • April 14 (Fri): WMF Holiday
  • May 1: Željko (Holidays in Croatia - Labor Day / May Day)
  • May 15?/16/17: Team offsite in Barcelona
  • May 18-20: Wikimedia Hackathon in Barcelona
  • May 21 (Mon): Tech-Mgt F2F
  • May 31: Željko (Holidays in Croatia - Corpus Christi)

Rotating positions[edit]


Maniphest query for deployment blocker tasks:
  • Feb 05 - wmf.20 - Chad
  • Feb 12 - wmf.21 - Mukunda
  • Feb 19 - wmf.22 - Mukunda
  • Feb 26 - wmf.23 - Tyler
  • Mar 05 - wmf.24 - Tyler
  • Mar 12 - wmf.25 - Chad
  • Mar 19 - wmf.26 - Chad
  • Mar 26 - wmf.27 - Mukunda
  • Apr 02 - wmf.28 - Mukunda
  • Apr 09 - wmf.29 - Tyler
  • Apr 16 - wmf.30 - Tyler


  • Feb 05 - Tyler
  • Feb 12 - Chad
  • Feb 19 - Chad
  • Feb 26 - Mukunda
  • Mar 05 - Mukunda
  • Mar 12 - Tyler
  • Mar 19 - Tyler
  • Mar 26 - Chad
  • Apr 02 - Chad
  • Apr 09 - Mukunda
  • Apr 16 - Mukunda

Team Business[edit]


Annual Plan[edit]

Mid-year check-ins[edit]

A basic check-in: Go over what we hoped we'd do when we talked back for annual review

Then, the outline from T&C:

  • Celebrate accomplishments (highs):
  • What can we learn from (lows):
  • What goals or projects have been completed? What went well, what could have been better?
  • What goals/responsibilities are still ahead? Is any support needed to help get them done? Does any work need to be adjusted (due to departmental/organizational change)?
  • Any peer feedback wanted or given? (Feel free to do this casually via email or conversation.)
    • [Greg: Let me know if anyone wants to do some kind of "ask your peers for feedback", I can set something up.]

Please come prepared to talk about those items; I'll be filling out a document we can look at during the meeting, just for our records. They are not shared with T&C (they will only be checking in with managers to verify the check-ins happened, not what the content was).

Scrum of Scrums[edit]

Greg to copy to etherpad after meeting:

This week[edit]

Release Engineering[edit]

  • Blocking
    • None?
  • Blocked
  • Updates

Last week[edit]

  • Blocking
  • Blocked
    • None
  • Updates:
    • Whole team back from offsite, slowly recovering from jet lag
    • wmf.20 rolling out this week as normal, deployments back to normal

Train status and happenings[edit]
Last week was **bad** (lots of failures, mostly fixed)
  • Two weeks off is a bummer
  • replag and operational issues
  • scary stuff is fixed, but there are stragglers
  • wmf.20 task still open for the stragglers
    • None of these are blockers for wmf.21

Past week status updates[edit]

All of it in table form:

Quarterly Goals[edit]

Program 1: Outcome 5: Milestone 1: Develop and migrate to a JavaScript-based browser testing stack[edit]

Due: End of this quarter
What: Specific improvements to the now canonical framework, see: task T182421, notably:
Upgrade webdriverIO to version 4.9
Investigate replacing nodemw with mwbot
Video recording for Selenium tests in Node.js
Task: task T182421
  • no progress, catching up (including on sleep) all week :(

Program 1: Outcome 5: Objective 1: Maintain existing shared Continuous Integration infrastructure[edit]

Draft requirements for a Kubernetes based solution for CI - task T183513
Migrate MediaWiki PHPUnit tests to Shipyard (docker-based CI) (~40% of Nodepool usage) - task T183512
Unify production and CI docker image build process - task T177276
Yes Done 01/15

Program 3: Outcome 1: Objective 2: Identify and find stewards for high-priority/high use code segment orphans[edit]

Due: End of quarter
task T174091
  • Next steps: apply feedbsck from discussion with Toby/Victoria to stewardship collateral. Start broad communication. Start filling gaps (fill in inaccuracies first, then for those that truly have no stewards, pull them into the stewardship review process)

Program 3: Outcome 2: Objective 2: Define and implement a process to regularly address technical debt across the Foundation[edit]

Due: End of quarter
task T174095
  • no progress.

Next steps: finish blog series on topic, setup regular SIG discussions on Tech Debt, reach out to teams to get in sync with how they are addressing exisitng tech debt.

Program 3: Outcome 2: Objective 3: Promote and surface important technical debt topics at large gatherings of Wikimedia developers (e.g., DevSummit and Hackathon(s))[edit]

Due: End of next quarter
task T174096
  • planning session for the May Hack-a-thon

Program 6: Outcome 2: Objective 2: Set up a continuous integration and deployment pipeline[edit]

Due: End of this quarter
Keyword: SSD
phab project:
Verify basic functionality of 'production' deployment and image (initially targeting mathoid):
Functional PoC within integration in the deployment-pipeline
Deploy to isolated k8s

Quaterly non-goal "Work"[edit]

Program 1: Outcome 1: Objective 1: Scap (Tech Debt Sprint FY201718-Q2)[edit]


Program 1: Outcome 5: Objective 1: Maintain existing shared Continuous Integration infrastructure[edit]

Program 1: Outcome 6: Milestone 1: Maintain Gerrit[edit]

Program 1: Outcome 6: Milestone 2: Maintain Phabricator[edit]

Streamline logspam workflows by adding some integration with phabricator
Store git-lfs (and other phab uploads) in swift: task T182085

Other work[edit]



  • What I plan to do
    • Migrate long tail of Nodepool based jobs to Docker containers
  • What I'm blocked on
    • Running MediaWiki tests in a Docker container. But I havent tried hard enough yet :D
  • Other?
    • Barely looking at Phabricator/IRC/email. Trying to focus.


  • What I plan to do
  • What I'm blocked on
    • Nothing really
  • Other?


  • What I plan to do
    • Continuing to integrate `helm test` into pipeline script
      • Service checker image was merged!
      • Going to work on getting blubber back on CI labs instances
      • Maybe I can start working on helm packaging
  • What I'm blocked on
    • Not technically blocked but need to work through blubber/python implementation decisions around image layer caching
  • Other?


  • What I plan to do
    • Get our Annual Plan segments into shape
      • meetings with others in Technology
  • What I'm blocked on
    • SRE on some annual plan program drafting
  • Other?
    • I've been having Annual Plan related dreams/nightmares, and clenching my jaw, way too much lately


  • What I plan to do
    • Summarize Stewardship Review discussion and set up meeting with Victoria and Toby
    • Plan/Prepare for Legacy encoding post portem
    • Set up post mortem for MediaWiki incident
    • Update stewardship content with feedback from Victoria/Toby
    • Logspam education
    • tech debt blog posts
  • What I'm blocked on
  • Other?


  • What I plan to do
    • train: 1.31.0-wmf.21 -
    • Phabricator deployment on wednesday.
      • This one might be a pain because there are a lot of database migrations.
    • Hopefully start working on swift for phabricator file storage which will enable us to use git-lfs in phab.
  • What I'm blocked on
    • No blockers
  • Other?



  • What I plan to do
    • T183456 Continuous integration for mediawiki-vagrant
    • T181284 Investigate replacing nodemw with mwbot
    • T182692 Document differences between Ruby and Node.js Selenium frameworks
    • T185094 Update page object pattern in Selenium tests
    • T185315 selenium-EXTENSION-jessie Jenkins job should have e-mail notification
  • What I'm blocked on
    • Chad/Mukunda/Tyler: how to run smoke tests during deployment?
  • Other?


Team Kanban Board Review and Triage[edit]

Once / month-ish review of backlog(s)[edit]

Kanban stats[edit]

Burnup chart