fdo-mirrors/mesa
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2025-12-20 16:00:08 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

ci: document process for disabling broken farms in more detail

Browse source 
Reading the previous version of the docs, I had the impression that the
correct action when a farm is broken is to ping Daniel or Emma in
the #freedesktop channel. I learned that just creating an MR to disable
it immediately is fine, and am documenting this. The farm maintainer
table also wasn't mentioned in the docs previously.

Signed-off-by: Olivia Lee <olivia.lee@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/35521>
This commit is contained in:
Olivia Lee 2025-06-13 12:47:37 -07:00
parent 6a77c8e953
commit e1856d7152
1 changed files with 11 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
docs/ci/index.rst
View file

@ -39,7 +39,11 @@ Under "CI / CD" → "General pipelines", make sure "Custom CI config path" is
empty (or set to the default ``.gitlab-ci.yml``), and that the empty (or set to the default ``.gitlab-ci.yml``), and that the
"Public pipelines" box is checked. "Public pipelines" box is checked.
If you're having issues with the GitLab CI, your best bet is to ask If a specific CI farm is failing for reasons unrelated to your changes, make an
MR to disable the farm following the `farm management <#farm-management>`__
instructions.
If you're having other issues with the GitLab CI, your best bet is to ask
about it on ``#freedesktop`` on OFTC and tag `Daniel Stone about it on ``#freedesktop`` on OFTC and tag `Daniel Stone
<https://gitlab.freedesktop.org/daniels>`__ (``daniels`` on IRC) or <https://gitlab.freedesktop.org/daniels>`__ (``daniels`` on IRC) or
`Emma Anholt <https://gitlab.freedesktop.org/anholt>`__ (``anholt`` on `Emma Anholt <https://gitlab.freedesktop.org/anholt>`__ (``anholt`` on
@ -68,7 +72,12 @@ When the farm starts failing for any reason (power, network, out-of-space), it n
git mv .ci-farms{,-disabled}/$farm_name git mv .ci-farms{,-disabled}/$farm_name
After farm restore functionality can be enabled by pushing a new merge request, which contains Find the GitLab handle of the farm's admin in ``.gitlab-ci/farm-rules.yml`` and
ping them on the MR. MRs to disable farms do not need to go through review, and
can be assigned to ``Marge`` directly.
After farm restore functionality can be enabled by pushing a new merge request,
which contains
.. code-block:: sh .. code-block:: sh