From 1f35b05ee5b43b8941aece1b8246650a33d1e49d Mon Sep 17 00:00:00 2001 From: Erik Faye-Lund Date: Mon, 28 Sep 2020 15:05:15 +0200 Subject: [PATCH] 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 Part-of: --- docs/ci/LAVA.rst | 4 ++-- 1 file 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