Lines Matching defs:CI
4 GitLab CI
11 and even then the MR CI runs in the forked repository, which might have been
14 The CI runs a number of tests, from trivial build-testing to complex GPU rendering:
26 Due to limited resources, we currently do not run the CI automatically
33 If the GitLab CI doesn't seem to be running on your fork (or MRs, as they run
35 Under "CI / CD" → "General pipelines", make sure "Custom CI config path" is
39 If you're having issues with the GitLab CI, your best bet is to ask
45 The three GitLab CI systems currently integrated are:
58 The CI replays application traces with various drivers in two different jobs. The first
87 to be added to the rules attribute of the Gitlab CI job that accesses the restricted
90 Intel CI
93 The Intel CI is not yet integrated into the GitLab CI.
95 `the Intel CI configuration repo <https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins>`__
96 if you think you or Mesa would benefit from you having access to the Intel CI).
102 The Intel CI runs a much larger array of tests, on a number of generations
116 If you're having issues with the Intel CI, your best bet is to ask about
122 CI farm expectations
128 driver had CI and failed once a week, we would be seeing someone's
151 If a HW CI farm goes offline (network dies and all CI pipelines end up
164 Mesa's CI is currently run primarily on packet.net's m1xlarge nodes
166 can speed up your personal CI builds (and marge-bot merges) by using a
186 The CI system uses Docker images extensively to cache
188 CI templates
215 Building locally using CI docker images
219 don't personally have. If you're experiencing this with the CI
231 .gitlab-ci.yml and run the CI meson build script: