Wikimedia Release Engineering Team/About
Appearance
Software we own
[edit]Deployment tools
[edit]- Scap – a tool deploy MediaWiki to both Kubernetes and bare-metal hosts. And to deploy services to bare-metal, non-Kubernetes hosts.
- WikimediaDebug – a browser plugin that allows users to debug web requests. We are the latest owners of WikimediaDebug, previously owned by the Performance Team.
Code hosting tools
[edit]- Gerrit – a website where Wikimedia hosts and code reviews some of its Git repositories. This is the primary code host for MediaWiki and extensions as well as WMF Puppet code.
- GitLab – a website where Wikimedia hosts and code reviews some of its Git repositories. This is the primary code host for services and toolforge tools.
Developer collaboration tooling
[edit]- Phabricator – Wikimedia's platform for tracking issues and project management of Wikimedia and related software. See Phabricator for more information. We are product owners of Phabricator in collaboration with SRE Collaboration Services who own the infrastructure.
- Patch Demo – a tool to build demo MediaWiki wikis with small tweaks to share with other users. We own this in collaboration with Developer Experience Test Platform.
- Catalyst – A web API used by Patch Demo to create MediaWiki instances in Kubernetes.
- MediaWiki dev-images – Docker images for running MediaWiki (and other services) on your local machine.
Production error handling
[edit]- Phatality – a plugin for OpenSearch. Used for reporting Wikimedia's MediaWiki production log message as tasks in Phabricator.
CI/CD tools for Gerrit
[edit]- Jenkins – a web service that runs tests for the code hosted in Gerrit.
- Zuul – a tool that sits between Gerrit and Jenkins. Whenever code is changed in Gerrit, Zuul will trigger Jenkins to test the code.
- Integration configuration – this is code that defines what tests run in Jenkins when a change is made in Gerrit.
- Quibble – a tool for efficiently running the MediaWiki test suite.
- Gerrit deployment pipeline – a suite of tools that publish Docker images from code hosted in Gerrit.
CI/CD tools for GitLab
[edit]- Blubber – software that builds Docker images from a YAML file. An alternative to using a Dockerfile. It enforces policies for our Docker images running in Wikimedia's production Kubernetes.
- Kokkuri – a testing and publishing suite for use in GitLab. It's intended to make it easy to use both GitLab and Blubber to produce Docker images.
- Reggie – a Docker image registry used for caching in our GitLab test infrastructure.
Processes we own
[edit]- Train deployment – once per week, all code used by Wikimedia's MediaWiki sites is bundled together and progressively deployed to all of our production wikis (including this one!)
- Backport deployment – many times per week, we deploy fixes or changes that cannot wait for the train deployment the following week.
- Gerrit privilege requests – a process where people can request a change in what they're able to do in or what they can access in our Gerrit system.
- GitLab access requests – a process where people can request a change in what they're able to do in or what they can access in our GitLab system.
Meeting archive
[edit]Each week Release Engineering publishes the notes from its check-in meeting. View our notes in our weekly check-in archive.
Accomplishments
[edit]Values
[edit]| Team Values | |||||
|---|---|---|---|---|---|
| 🧑💻 Developer focus | 🎖️Integrity | 🌻 Freedom & open source | 🙌 Quality | 👥 Teamwork & Collaboration | |
|
|
|
|
| |