Jump to content

Wikimedia Release Engineering Team/Pretrain/Progress reports/2026-07-03

From mediawiki.org

Report on activities in the Pretrain project for the week ending 2026-07-03.

[WE6.7.2 / ST5.1.1] Routing test

[edit]

If we create the Pretrain deployment environment using existing production MediaWiki container images and begin routing testwiki traffic to it, we will develop confidence that our routing design is sufficiently complete to support the full Pretrain MVP (e.g., all testwiki traffic is reliably served by the Pretrain environment and container).

Progress update
  • Stage: Engineering/Development
  • As we cross the fiscal year boundary and switch to a newer version of annual planning, this hypothesis is renumbered from the Fiscal Year 2025-2026 WE6.7.2 to the Fiscal Year 2026-2027 ST5.1.1.
  • This week, work continued on mw-pretrain service turnup (T427668). While the necessary changes to bring up a "pilot" service have started to land, there remain a handful of minor issues to resolve before it becomes available for initial testing.
Any new metrics related to the hypothesis
  • None
Any emerging blockers or risks
  • Not yet
Any unresolved dependencies - do you depend on another team that hasn’t already given you what you need? Are you on the hook to give another team something you aren’t able to give right now?
  • No
Have there been any new lessons from the hypothesis?
  • Not yet
Have there been any changes to the hypothesis scope or timeline?
  • No

[WE6.7.3 / ST5.1.2] Automated supervision

[edit]

If we implement an initial set of automated supervision strategies and enable automated deployment to the Pretrain environment for the routing test, we will develop confidence that automated supervision is ready to serve as our primary risk mitigation for the full Pretrain MVP (e.g., false positives are understood, and we have identified a path to mitigate them).

Progress update
  • Stage: Engineering/Development
  • As we cross the fiscal year boundary and switch to a newer version of annual planning, this hypothesis is renumbered from the Fiscal Year 2025-2026 WE6.7.3 to the Fiscal Year 2026-2027 ST5.1.2.
  • Bryan spent time getting caught up on discussions and decisions made during his vacation.
  • Ahmon started looking into allowing different configuration for tests and checks based on the target deployment environment (T428971).
Any new metrics related to the hypothesis
  • None
Any emerging blockers or risks
  • Not yet
Any unresolved dependencies - do you depend on another team that hasn’t already given you what you need? Are you on the hook to give another team something you aren’t able to give right now?
  • No
Have there been any new lessons from the hypothesis?
  • Not yet
Have there been any changes to the hypothesis scope or timeline?
  • No