Wikimedia Release Engineering Team/Checkin archive/20171204

From mediawiki.org

2017-12-04[edit]

Vacations/Important dates[edit]

https://office.wikimedia.org/wiki/HR_Corner/Holiday_List
How to do it
  • Dec 4th (Monday): Antoine - no train were available from Paris to my city!
  • Dec 11-13th - Chad. Maybe? Friend might be flying into town and I need to play tour guide if so
  • December Fridays - Greg is taking off
  • December 25 (Monday): Ĺ˝eljko - holiday (Christmas Day)
  • December 26 (Tuesday): Ĺ˝eljko - holiday (St Stephen's Day)
  • Dec 25-Jan 1 - End of year/new year holidays
  • January 1 (Monday): Ĺ˝eljko - holiday (New Year's Day)

Team Business[edit]

Rotating positions and absences[edit]

Maniphest query for deployment blocker tasks: https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-fmcvjrkfvvzz3gxavs3a&statuses=open%28%29&group=none&order=newest#R

Dec 4 and Dec 11[edit]

  • Train: Chad
  • SoS: Mukunda
  • Out
    • Dec 4th (Monday): Antoine

Dec 18 and Dec 25[edit]

  • Train: NO ONE!
  • SoS: Chad
  • Out:
    • Dec 25-Jan 1 - End of year/new year holidays
    • December 25 (Monday): Ĺ˝eljko - holiday (Christmas Day)
    • December 26 (Tuesday): Ĺ˝eljko - holiday (St Stephen's Day)
    • Antoine - not sure yet of the exact dates


Jan 1 and Jan 8[edit]

  • Train: Mukunda
  • SoS: Tyler
  • Out:
    • January 1 (Monday): Holiday, everyone

Actions from last meeting[edit]

  • ACTION: git-lfs in Gerrit
    • a test repo was created
    • question: git-lfs supports objects that are <= 2GB ... is that a problem?
    • phab side: still need to enable it and figure out storage backend
    • ACTION: see if the 2 gig limit is real :)
      • there's a config thing

Scrum of Scrums[edit]

This week[edit]

Release Engineering[edit]

  • Blocking
  • Blocked
  • Updates
    • [MW Train] Reminder! This is your last few weeks of deployments for the year/quarter! No non-emergency deploys starts the week of December 18th. [wiki][email]
    • [MW Train] The post mortem for T181006 (Watchlist and RecentChanges failure due to ORES on frwiki and ruwiki) is scheduled for December 7th.
    • #mw-1.30-release MediaWiki 1.30 is about to be released in the next few days, so last call for any blockers people might have...you know...forgotten

Last week[edit]

  • Blocking
  • Blocked
  • Updates
    • [MW Train] Reminder! This is your last few weeks of deployments for the year/quarter! No non-emergency deploys starts the week of December 18th. [wiki][email]
    • [MW Train] The post mortem for T181006 (Watchlist and RecentChanges failure due to ORES on frwiki and ruwiki) is scheduled for December 7th.
    • [Sunsetting WG] Meeting with Victoria and Toby tomorrow (Wednesday).
    • [nodejs browser tests] CirrusSearch and Mobile are active with migrations.
    • [nodejs browser tests] Investigation of using mwbot instead of nodemw (javascript api interfaces to MW). CirrusSearch uses mwbot. We use nodemw (maintained by a Wikia engineer).
    • [ruby] We will upgrade rubocop (Ruby linter/static analyzer) across the corpus of extensions due to a security issue (pointed out by the new Github security issue notification service). We (WMF production and CI) are not affected by the issue AND we have officially deprecated our ruby browser test stack (where 99% of all rubocup uses/dependencies are) BUT we’ll do it :) [wiki][email]
    • [techdebt] Wider conversations regarding SLAs/stewardship of components/software: https://www.mediawiki.org/wiki/Talk:Development_policy/Code_Stewardship
    • [techdebt] 2nd of the 3 tech debt series of blog posts (after the 0th introduction one on Code Health) is in drafting.
    • [CI] We’ve migrated almost all of the tox (python) jobs to the new container based CI infra.


Puppet SWAT[edit]

list of patches you want to submit to Puppet SWAT


Logspam \ Last week's train updates[edit]

https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Roles#Train_Conductor

Other Team Business[edit]


Q3 goals! :) :)[edit]

https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201718Q2
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201718Q3


Program 1: webdriver.io[edit]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Technology#Program_1:_Availability.2C_performance.2C_and_maintenance
  • update to recent version of webdriver.io
  • video recordings
  • cucumber support
  • cleanup of some hardcoded urls


  • composer support (instead of vendor)
  • Jan is adding wdio/selenium tests to wikimedia/portals
Program 3: Tech Debt[edit]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Technology#Program_3:_Addressing_technical_debt

Outcome 1

  • Objective 2: Identify and find stewards for high-priority/high use code segment orphans - task T174091
  • Objective 3: Define and steward a light-weight process for adopting or orphaning/sunsetting products and infrastructure.
    • This is done by the Sunsetting working group

Outcome 2

  • Objective 2: Define and implement a process to regularly address technical debt across the Foundation
  • Objective 3: Promote and surface important technical debt topics at large gatherings of Wikimedia developers (e.g., DevSummit and Hackathon(s))


Program 6: SSD[edit]
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Final/Programs/Technology#Program_6._Streamlined_service_delivery


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


Program 1: Outcome 5: Objective 1: Maintain existing shared Continuous Integration infrastructure =[edit]
Goal: A generalized POC for a docker-based CI.
https://phabricator.wikimedia.org/project/view/3008/ (shipyard workboard)


Program 1: Outcome 5: Objective 1: MW Nightlies server[edit]
  • chad point on this, bulk of time


Q2 goal/project check-in[edit]

All of it in table form: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Goals/201718Q2

Quarterly Goals[edit]

Program 1: Outcome 5: Milestone 1: Migrate majority of developers to JavaScript based browser test framework (webdriver.io)[edit]

Due: End of this quarter
Quarter Goal Task: Port Selenium tests from Ruby to Node.js - task T139740
  • T139740 Port Selenium tests from Ruby to Node.js
    • T174591 Flow: Migrate browser tests from Ruby to node.js
      • Deleting tests
    • T171848 Port Echo Selenium tests from Ruby to Node.js
      • Probably deleting tests too
  • T181285 Replace jshint with eslint in nodemw
    • Done. Merged upstream.
  • T180144 Upgrade WebdriverIO to 4.9
    • Found the upstream commit that broke our tests. Next step is reporting upstream.
Ruby[edit]
  • T180878 Upgrade RuboCop and Rubyzip across the extension fleet
    • In progress. A couple of repos already causing trouble. :|

Program 3: Outcome 1: Objective 1: Define a set of code stewardship levels (from high to low expectations)[edit]

Due: End of this quarter
Quatertly Goal task: - task T174090
  • Continued discussion of what Stewardship means. Some of the feedback suggests that "stewardship" may be too soft of a word, perhaps "ownership" is better.

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

Due: End of next quarter
Quaterly Goal task - task T174091
  • Restarted clean-up/gap filling for developers/maintainers page.

Program 3: Outcome 2: Objective 1: Define a “Technical Debt Project Manager” role that regularly communicates with all Foundation engineering teams regarding their technical debt[edit]

Due: End of this quarter


  • done

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

Due: End of next quarter
  • Blog post 2 of 3 almost done.


Program 6: Outcome 2: Objective 2: Set up a continuous integration and deployment pipeline to publish new versions of an application to production via testing and staging environments that reliably reproduce production[edit]

Due: End of this quarter
Keyword: SSD
Complete build phase of release pipeline
    • Build test variant
    • Run test entrypoint w/developer feedback - services dependency
    • Build production variant w/developer feedback - services dependency
    • Tag production container
    • Push to production docker registry - ops dependency - staging namespace
Tracking: https://phabricator.wikimedia.org/T157469
current status: https://phabricator.wikimedia.org/project/view/2453/
  • npm is bologna

Quaterly non-goal "Work"[edit]

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

workboard


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

Goal: A generalized POC for a docker-based CI.
https://phabricator.wikimedia.org/project/view/3008/ (shipyard workboard)
DONE
  • being generalized
  • more infra work needed such as:
    • gotta move toward kubernetes
    • docker-pkg and work closely with SSD / ops


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

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

Program 1: Outcome 5: Objective 1: MW Nightlies server[edit]

Other work[edit]

  • TestED
    • Zeljko and JR are working to develope some testing education material primarily focused on helping developers test for effectively.
    • Zeljko, Cormac, and JR are exploring ways to introduce TDD to WMF teams.
      • General ED on TDD -> MediaWiki specific support (tech sessions)


Grooming[edit]

Team Kanban Board Review and Triage[edit]


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


Kanban stats[edit]

Burnup chart
Retrieved from "https://www.mediawiki.org/w/index.php?title=Wikimedia_Release_Engineering_Team/Checkin_archive/20171204&oldid=3615531"