Lines Matching full:gitlab
4 The bare-metal scripts run on a system with gitlab-runner and Docker,
18 This testing requires power control of the DUTs by the gitlab-runner
22 We require access to the console output from the gitlab-runner system,
28 gitlab-runner system, since Mesa often needs to update the kernel either for new
32 artifacts on GitLab, and so that we can download traces (too large for an
37 See ``src/freedreno/ci/gitlab-ci.yml`` for an example of fastboot on DB410c and
46 gitlab-runner mounts the runner's tftp directory specific to the board
56 the dnsmasq.conf.d in the Google farm, with the gitlab-runner host we
77 See ``src/freedreno/ci/gitlab-ci.yml`` for an example of Servo on cheza. Note
86 - x86-64 gitlab-runner machine with a mid-range CPU, and 3+ GB of SSD storage
99 using a "mesaci" community name that the gitlab runner can access as its
132 See ``src/broadcom/ci/gitlab-ci.yml`` and ``src/nouveau/ci/gitlab-ci.yml`` for an
138 Each board will be registered in freedesktop.org GitLab. You'll want
143 sudo gitlab-runner register \
144 --url https://gitlab.freedesktop.org \
158 The registration token has to come from a freedesktop.org GitLab admin
159 going to https://gitlab.freedesktop.org/admin/runners
174 more customization in ``/etc/gitlab-runner/config.toml``. First, add
176 this many jobs running managed by this gitlab-runner"). Then for each
189 gitlab-runner restart``