Wikimedia Release Engineering Team/Group -1/Progress reports/2024-10-24

← week ending 2024-10-17

Group -1 progress reports week ending 2024-10-24

week ending 2024-10-31 →

Report on activities in the Group -1 project for the week ending 2024-10-24.

[WE6.2.1] Publish pre-train single version containers

Tracked in Phabricator
Task T369115

If we publish a versioned build of MediaWiki, extensions, skins, and Wikimedia configuration at least once per day we will uncover new constraints and establish a baseline of wallclock time needed to perform a build.

Progress update

• Stage: Deployment/Scaling
• 🎉 The team's work has produced an end-to-end working implementation that:
  • creates or updates a wmf/next branch in MediaWiki core, each extension, and each skin deployed to Wikimedia wikis
  • updates submodules in the MediaWiki core repo's wmf/next branch to point to the equivalent extension and skin branches
  • builds an OCI container image from the MediaWiki core repo's wmf/next plus configuration, security patches, and production secrets
  • publishes the new image to the Wikimedia production container registry
• Project artifacts:
  • MediaWiki branch and publish WMF single-version image job running on releases-jenkins (branchMWSingleVersion.groovy source)
  • MediaWiki publish WMF single-version image job running on releases-jenkins (publishMWSingleVersion.groovy source)

The planned technical work for the hypothesis has now been completed. The implemented job pipeline will continue to run once per day for the foreseeable future. Each successful run will provide additional data on wallclock runtime. Each failed run will guide us towards identifying operational challenges for the pipeline.

We expect to follow up with additional hypothesis work this quarter to complete strategic and high level tactical planning focused on reaching the major project goal of creating the most "production like" environment for QTE staff to use for testing and automated regression checks prior to train deployment to major content wikis.

Any new metrics related to the hypothesis

• MediaWiki branch and publish WMF single-version image job average wallclock runtime: 41 minutes
• MediaWiki publish WMF single-version image job average wallclock runtime: 23 minutes
• Total average pipeline runtime: 64 minutes

Any emerging blockers or risks

• None

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?

• None

Have there been any new lessons from the hypothesis?

• No

Have there been any changes to the hypothesis scope or timeline?

• No