Wikimedia Release Engineering Team/Group -1/Progress reports/2024-08-29
| â week ending 2024-08-22 | Group -1 progress reports week ending 2024-08-29 | week ending 2024-09-05 â |
Report on activities in the Group -1 project for the week ending 2024-08-29.
[WE6.2.1] Publish pre-train single version containers
[edit]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
- Dan wrote a Jenkins job that will create or update a "wmf/next" branch when run. This branch will be the basis for our daily image build milestone.
- The team discussed some tangentially related (but out of scope for this hypothesis) issues and ideas related to updating scap to support producing additional container images which vary on base image. This is how folks are currently imagining that we will handle things like PHP version upgrades which will need some amount of "test in production" usage before being made the default for all MediaWiki pods in the WikiKube Kubernetes cluster.
- Any new metrics related to the hypothesis
-
- None
- 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?
-
- No