[Mesa-dev] GitLab CI is now opt-in - tl;dr: push to ci/*

Eric Engestrom eric.engestrom at intel.com
Tue Feb 19 17:05:33 UTC 2019

Hi all,

The GitLab CI translated from Travis is really resource-hungry (see the
discussion DanielS started [1]).

Efforts are ongoing to make it nicer to its runners, but as
a (hopefully) temporary measure, the CI is now opt-in to avoid wasting
cycles if the dev pushing commits didn't want to run it through the CI

If you're interested, the actual change is here:

Technically, the CI now runs automatically on master and merge requests,
and you can always trigger builds manually by going on your fork's
(or use an app like `lab` [2] which uses the GitLab API)

But to make it easier, you can also push to any branch starting with
`ci/*` or `ci-*`, or a branch simply named `ci`, and the CI will run
automatically on it.

I'm sure I'm breaking someone's workflow [3], but remember that the plan
is to tame this CI beast and turn it back on for everything :)


[1] https://lists.freedesktop.org/archives/mesa-dev/2019-February/215481.html
[2] https://github.com/zaquestion/lab
[3] https://xkcd.com/1172/

More information about the mesa-dev mailing list