Lines Matching full:gitlab

4 GitLab CI
7 GitLab provides a convenient framework for running commands in response to Git pushes.
23 if the GitLab runners are overwhelmed, which happens sometimes. When it does happen,
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/``.
33 If the GitLab CI doesn't seem to be running on your fork (or MRs, as they run
36 empty (or set to the default ``.gitlab-ci.yml``), and that the
39 If you're having issues with the GitLab CI, your best bet is to ask
41 <https://gitlab.freedesktop.org/daniels>`__ (``daniels`` on IRC) or
42 `Eric Anholt <https://gitlab.freedesktop.org/anholt>`__ (``anholt`` on
45 The three GitLab CI systems currently integrated are:
58 The Intel CI is not yet integrated into the GitLab CI.
60 `the Intel CI configuration repo <https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins>`__
71 `Crucible <https://gitlab.freedesktop.org/mesa/crucible>`__,
74 `Piglit <https://gitlab.freedesktop.org/mesa/piglit>`__,
83 <https://gitlab.freedesktop.org/craftyguy>`__ (``craftyguy`` on IRC) or
84 `Nico Cortes <https://gitlab.freedesktop.org/ngcortes>`__ (``ngcortes``
135 faster personal machine as a runner.  You can find the gitlab-runner
136 package in Debian, or use GitLab's own builds.
138 To do so, follow `GitLab's instructions
139 <https://docs.gitlab.com/ce/ci/runners/#create-a-specific-runner>`__ to
140 register your personal GitLab runner in your Mesa fork.  Then, tell
143 lines in ``/etc/gitlab-runner/config.toml``, for example::
157 <https://gitlab.freedesktop.org/freedesktop/ci-templates/>`_ help us
165 not, the associated `.gitlab-ci/containers/<jobname>.sh`` will be run
177 <https://gitlab.freedesktop.org/mesa/mesa/container_registry>`_ for
199 .gitlab-ci.yml and run the CI meson build script:
205 …sabled -D egl=enabled -D platforms=android" CROSS=aarch64-linux-android ./.gitlab-ci/meson-build.sh