Lines Matching +full:gitlab +full:- +full:ci

1 LAVA CI
13 -------------------
14 - Collabora `[dashboard] <https://lava.collabora.dev/scheduler/device_types>`__ (without authentica…
15 - Lima [dashboard not available]
17 Mesa-LAVA software architecture
18 -------------------------------
20 The gitlab-runner will run on some host that has access to the LAVA
21 lab, with tags like "mesa-ci-x86-64-lava-$DEVICE_TYPE" to control only
23 gitlab-runner spawns a Docker container with lavacli in it, and
31 Deploying a new Mesa-LAVA lab
32 -----------------------------
39 The device type in lava-gitlab-ci.yml is the device type you create in
41 ``/etc/lava-dispatcher/device-types``.  You create your boards under
46 ``/etc/lava-dispatcher/device-types``).  Now, go find a relevant
52 to connect Mesa CI to it.  Install gitlab-runner and register as a
53 shared runner (you'll need a GitLab admin for help with this).  The
54 runner *must* have a tag (like "mesa-ci-x86-64-lava-rk3399-gru-kevin")
56 across ``gitlab.freedesktop.org``, and your runner isn't ready for
62 ``/etc/gitlab-runner/config.toml`` so it can access localhost.  Create a
63 gitlab-runner user in your LAVA instance, log in under that user on
67 .. code-block:: yaml
72       username: gitlab-runner
75 ``/etc/gitlab-runner/config.toml`` so that the Docker container can
78    volumes = ["/home/anholt/lava-config/lavacli.yaml:/root/.config/lavacli.yaml", "/cache"]
82 GitLab CI YAML, but this way the current method of connecting to the
84 relevant as we have many stable branches all using CI).
86 Now it's time to define your test jobs in the driver-specific
87 gitlab-ci.yml file, using the device-specific tags.