summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorErik Faye-Lund <erik.faye-lund@collabora.com>2020-09-28 15:05:15 +0200
committerMarge Bot <eric+marge@anholt.net>2021-04-01 08:33:41 +0000
commit1f35b05ee5b43b8941aece1b8246650a33d1e49d (patch)
tree0f7ec95181ab0f4f1d2ff8fe12e92fe2d11bd420 /docs
parent69b25cee3bb735dac64a2bb7c9952f046a45aba8 (diff)
docs: spell out full name of gitlab instance
While we're at it, quote it so it's clear that it's something special. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9947>
Diffstat (limited to 'docs')
-rw-r--r--docs/ci/LAVA.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ci/LAVA.rst b/docs/ci/LAVA.rst
index 206e1013244..c5aa1e4b8af 100644
--- a/docs/ci/LAVA.rst
+++ b/docs/ci/LAVA.rst
@@ -47,8 +47,8 @@ Once you can boot your board using a custom job definition, it's time
to connect Mesa CI to it. Install gitlab-runner and register as a
shared runner (you'll need a GitLab admin for help with this). The
runner *must* have a tag (like "mesa-lava-db410c") to restrict the
-jobs it takes or it will grab random jobs from tasks across fd.o, and
-your runner isn't ready for that.
+jobs it takes or it will grab random jobs from tasks across
+``gitlab.freedesktop.org``, and your runner isn't ready for that.
The runner will be running an ARM Docker image (we haven't done any
x86 LAVA yet, so that isn't documented). If your host for the