Wikimedia Release Engineering Team/Checkin archive/2022-06-01

From mediawiki.org


2022-06-01[edit]

✨Values✨[edit]

  • Stay Cool: Keep it ________ Together
  • Precious Moments: ______time Quality
  • Star trek might say the shield's structural _______ is at 15% Integrity
  • What a camera lens does on a subject, and we do on developers: _____ Focus
  • _______ of the press foundation protects journalist's rights Freedom

ERC Update[edit]

  • Submitted our feedback

Team API[edit]

https://docs.google.com/document/d/1KoWCLyhHbekAf8OTmtDnCvNzssCnzEv479et9ljhhvs/edit#

🏆 Wins[edit]

https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Monthly_notable_accomplishments
May '22 edition
  • Our long, grinding efforts at deployment training are finally starting to result in more people doing deploys (well, ok, they've resulted in Clare doing deploys, anyway) \o/
  • Rolled back train five times
  • Deployment tooling just kind of sucks less than it used to
  • Merged scap backport
  • scap stage-train \o/
  • Finally got rid of the generic service-pipeline-* jobs and migrated remaining 23 projects to use bespoke `.pipeline/config.yaml` based jobs
  • gitlab-a-thon
    • We found a a whooooole lot of blockers
    • Dan being a good open-source citizen: https://github.com/moby/buildkit/pull/2868
      • JWT implements oauth2
      • Could be used to authorize push access to namespace based on project path
  • Root access on phabricator
  • Updated Jenkins for Security—which broke Jenkins for a while
  • I think I finally remember how to use a standalone puppetmaster
  • ERC going well and DEI moving ahead
  • Dan got changes to buildkit merged upstream
  • Seems like we're pretty close to how auth will work for publishing images from GL
  • serviceops are plodding ahead on GitLab physical machines
  • CI for blubber in gitlab
  • update scap backport to work with new zuul plugin
  • new tests for scap backport
  • scap tests run without deprecation warnings (for stretch, buster, and bullseye)
  • Giuseppe plans to enable always-restart-php-fpm on Thursday.
  • Docs for GitLab are somewhat less crappy than they were a week ago
  • Upgraded Gerrit in train-dev to match production
  • Hired Chad
June '22 edition

😶 Let's keep this empty[edit]

📅 Vacations/Important dates[edit]

https://office.wikimedia.org/wiki/HR_Corner/Holiday_List#2022
https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Time_off

June[edit]

  • ~9-10 Jun: Brennen (🔥⛺) (probably ((maybe)))
  • 15-17 Jun: Dan (🎒⛰)
  • 20 Jun: Juneteenth (observed) (U.S. Staff with Reqs)
  • 22 Jun: Brennen out afternoon
  • 20-30 Jun: Jaime

July[edit]

  • 1 Jul: Jaime; Dan (🏔)
  • 4 Jul: US Independence day (U.S. Staff with Reqs)
  • 25-29 Jul: Dancy out
  • ~29 Jul: Brennen (🪕)

August[edit]

  • Antoine: some weeks
  • 9 Aug: International Day of the World’s Indigenous Peoples
  • 12 Aug: Brennen (🎸)
  • 27-31 Aug: Brennen (🔥)

September[edit]

  • 5 Sept: U.S. Labor Day (U.S. Staff with Reqs)
  • 1-6 Sept: Brennen (🔥)
  • ~14-18 Sept: Brennen (⛺🪕)

🔥🚂 Train[edit]

https://tools.wmflabs.org/versions/
https://train-blockers.toolforge.org/
https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar


  • 2 May – wmf.10 – Antoine + Brennen
  • 9 May - wmf.11 – Skipping for GitLab-a-thon
  • 16 May - wmf.12 - Jaime + Antoine
  • 23 May - wmf.13 - Ahmon + Jaime (Antoine out)
  • 30 May - wmf.14 - Jeena + Ahmon
  • 6 Jun - wmf.15 - Dan + Jeena (Brennen out)
  • 13 Jun - wmf.16 - Brennen + Jeena (Dan out)
  • 20 Jun - wmf.17 - Antoine + Brennen (Jaime out)
  • 27 Jun - wmf.18 - Dan + Antoine (Jaime out)
  • 4 Jul - wmf.19 - Jaime + Dan
  • 11 Jul - wmf.20 - Ahmon + Jaime
  • 18 Jul - wmf.21 - Jeena + Ahmon
  • 25 Jul - wmf.22 - Brennen + Jeena
  • 1 Aug - wmf.23 - Antoine + Brennen
  • 8 Aug - wmf.24 - No train (Brennen out)
  • 15 Aug - wmf.25

Hiring Update[edit]

Content-admins request[edit]

🏃🤔 Sprint planning, planning[edit]

What's the most important thing for the team to swarm in the next two weeks? What should be our one focus?
Proposed Process:
  • 5 minutes: add all your things here
  • 15 minutes to discuss everything here
  • 5 minutes to vote (2 things)
  • Next Wednesday, kick off?