From: Eric Anholt Date: Mon, 20 Jul 2020 16:32:16 +0000 (-0700) Subject: docs: Explain how to set up a personal gitlab runner. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=7f40db42a2d8af9565f5338acd96afb56d6f85b9;p=mesa.git docs: Explain how to set up a personal gitlab runner. I'm not the only one doing it, so document it, especially since there's a new trick as of https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5669 Reviewed-by: Andres Gomez Part-of: --- diff --git a/docs/ci/index.rst b/docs/ci/index.rst index 7e01840b857..22e697b3d8b 100644 --- a/docs/ci/index.rst +++ b/docs/ci/index.rst @@ -126,6 +126,28 @@ report to mesa-dev@lists.freedesktop.org after the fact explaining what happened and what the mitigation plan is for that failure next time. +Personal runners +---------------- + +Mesa's CI is currently run primarily on packet.net's m1xlarge nodes +(2.2Ghz Sandybridge), with each job getting 8 cores allocated. You +can speed up your personal CI builds (and marge-bot merges) by using a +faster personal machine as a runner. You can find the gitlab-runner +package in debian, or use gitlab's own builds. + +To do so, follow `gitlab's instructions +`__ to +register your personal gitlab runner in your Mesa fork. Then, tell +Mesa how many jobs it should serve (``concurrent=``) and how many +cores those jobs should use (``FDO_CI_CONCURRENT=``) by editing these +lines in ``/etc/gitlab-runner/config.toml``, for example:: + + concurrent = 2 + + [[runners]] + environment = ["FDO_CI_CONCURRENT=16"] + + Docker caching --------------