ベータクラスター

グループ:	Developer Experience
開始:	2012-03-01
リーダー:	Levi Ferreira

This page is a translated version of the page Beta Cluster and the translation is 74% complete.

The Beta Cluster is a functional, production-like environment in the Cloud VPS that is suitable for final-stage testing of new features. It was initially created as a way to provide an exact copy of the WMF production cluster (including db hosts, apaches, logging, squids, varnish caching, image scalers, etc.) using Cloud VPS instances.

Current Status

Beta Cluster remains a significant part of MediaWiki's development ecosystem, serving as a pre-production environment to test and deploy code before it reaches production, reshaped its purpose and management but is largely unmaintained.

In 2024, the Developer Experience group took Product Stewardship of Beta Cluster^[1] and are currently focused on giving it clear direction and narrowing its use cases. The long-term goal is to transform the Beta Cluster into a Playground environment for experimentation and testing without replicating every aspect of production. As part of this effort, the team is also working actively on tools like PatchDemo/Catalyst to ensure the most common use cases of Beta are covered as on-demand isolated testing environments. While this transformation is ongoing, the team is prioritizing only very essential updates (E.g. PHP 8.1 Upgrade) and not addressing smaller issues in its current state.

Developer Experience encourage users of Beta Cluster to submit a feature request in Phabricator if their requirements are not adequately addressed yet by PatchDemo/Catalyst or other tools. Their input will guide improvements and help prioritize features.

How it works

Git master の外部で実行し、固有の MediaWiki コアが存在し、拡張コードはおよそ10分ごとに更新されます。ベータクラスターはWikimedia テストウィキのひとつ。制作と別に固有のSULログインを採用、そこでたとえばen.wikipedia.beta.wmflabs.org で設定したアカウントはen.wikisource.beta.wmflabs.org でも有効だが、他の制作型ウィキでは無効です。

設定の概要を参照。

Open tasks

Open tasks can be found in the workboard in Phabricator. Those task are currently used as a way to catalogue issues or recurring problems, but are not addressed or observed immediately.