Lines Matching +full:download +full:- +full:git +full:- +full:cache
5 ---------
7 GitLab provides a convenient framework for running commands in response to Git pushes.
8 We use it to test merge requests (MRs) before merging them (pre-merge testing),
9 as well as post-merge testing, for everything that hits ``main``
14 The CI runs a number of tests, from trivial build-testing to complex GPU rendering:
16 - Build testing for a number of build systems, configurations and platforms
17 - Sanity checks (``meson test``)
18 - Some drivers (softpipe, llvmpipe, freedreno and panfrost) are also tested
19 using `VK-GL-CTS <https://github.com/KhronosGroup/VK-GL-CTS>`__
20 - Replay of application traces
30 If you're interested in the details, the main configuration file is ``.gitlab-ci.yml``,
31 and it references a number of other files in ``.gitlab-ci/``.
36 empty (or set to the default ``.gitlab-ci.yml``), and that the
51 bare-metal
56 -------------------------
59 job replays traces listed in ``src/<driver>/ci/traces-<driver>.yml`` files and if any
61 ``src/<driver>/ci/restricted-traces-<driver>.yml`` and it is allowed to fail. This second
62 job is only created when the pipeline is triggered by `marge-bot` or any other user that
65 A traces YAML file also includes a ``download-url`` pointing to a MinIO
66 instance where to download the traces from. While the first job should always work with
72 contributors without permissions to download non-redistributable traces can be merged
75 As an aside, only maintainers of such non-redistributable traces are responsible for
77 download and test them by themselves.
80 non-redistributable traces can request permission to Daniel Stone <daniels@collabora.com>.
84 https://gitlab.freedesktop.org/freedesktop/helm-gitlab-config/-/commit/a3cd632743019f68ac8a829267de…
91 --------
97 Results can be seen on `mesa-ci.01.org <https://mesa-ci.01.org>`__
100 `mesa-ci-results.jf.intel.com <http://mesa-ci-results.jf.intel.com>`__.
107 `VK-GL-CTS <https://github.com/KhronosGroup/VK-GL-CTS>`__,
117 it on ``#dri-devel`` on OFTC and tag `Nico Cortes
120 .. _CI-farm-expectations:
123 --------------------
133 turnaround time that we can get our MRs through marge-bot without the
144 .. code-block:: yaml
157 report to mesa-dev@lists.freedesktop.org after the fact explaining
162 ----------------
166 can speed up your personal CI builds (and marge-bot merges) by using a
167 faster personal machine as a runner. You can find the gitlab-runner
171 <https://docs.gitlab.com/ce/ci/runners/#create-a-specific-runner>`__ to
175 lines in ``/etc/gitlab-runner/config.toml``, for example::
184 --------------
186 The CI system uses Docker images extensively to cache
187 infrequently-updated build content like the CTS. The `freedesktop.org
189 <https://gitlab.freedesktop.org/freedesktop/ci-templates/>`_ help us
192 apt cache, and other such common pitfalls of building Docker images).
197 not, the associated `.gitlab-ci/containers/<jobname>.sh`` will be run
202 container update from the same day, you will get a Git conflict
206 bump the tag on each ``git commit --amend`` to your development
216 ---------------------------------------
223 Pulling docker image registry.freedesktop.org/anholt/mesa/debian/android_build:2020-09-11
227 go in _build, according to ``meson-build.sh``). We're going to be
228 using the image non-interactively so we use ``run --rm $IMAGE
229 command`` instead of ``run -it $IMAGE bash`` (which you may also find
231 .gitlab-ci.yml and run the CI meson build script:
233 .. code-block:: console
235 IMAGE=registry.freedesktop.org/anholt/mesa/debian/android_build:2020-09-11
237 …--rm -v `pwd`:/mesa -w /mesa $IMAGE env PKG_CONFIG_PATH=/usr/local/lib/aarch64-linux-android/pkgco…
242 .. code-block:: console
244 sudo docker run --rm -v `pwd`:/mesa $IMAGE ninja -C /mesa/_build
248 -----------------
260 -------------------------------
262 Gitlab CI usually runs a bleeding-edge kernel. The following documentation has