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

← week ending 2024-10-03

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

week ending 2024-10-17 →

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

[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: Engineering/Development
• The team discussed the T376023: Not all users with deployer rights are in the docker group issue discovered last week. The agreed upon plan is to reintroduce the containerized runtime for processing PHP code with an optional sudo wrapper to execute the container as the privileged mwbuilder user. New scap sub-commands will be introduced to serve as the sudo execution target.
• Ahmon removed the legacy ability to inject new scripts into scap as user defined plugins. This reduces the risk of abuse of a sudo wrapper.
• The team is now estimating completion of this hypothesis by the end of October 2024 (~3 more weeks). There is some hope that we will actually wrap up implementation sooner than that date, but we would rather under promise and over deliver than underestimate the time needed.
• Tyler and Bryan have started working to define the next hypothesis that will follow this one. That hypothesis would be expected to be completed by the end of December 2024 and will likely focus on strategic and tactical planning of additional work that would be implemented in FY24/25 Q3 (January-March 2025) or later.

Any new metrics related to the hypothesis

• The wmf/next branching job is showing a stable wallclock time of 8 to 8.5 minutes across nearly 30 runs. While we are targeting a cadence of once per day this performance will be acceptable. When we start to ramp up the frequency of branch cuts we can consider prioritizing improvements in the branch cut procedure that would reduce the time needed to perform each iteration.

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?

• Not yet

Have there been any new lessons from the hypothesis?

• No

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

• The timeline estimate has been updated to end of October 2024.