I just merged https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2794 , which affects people who want to run the CI pipeline on personal Mesa branches:
Pushing changes to a personal branch now always creates a pipeline, but none of the jobs in it run by default. (There are no longer any special branch names affecting this, because creating MRs from such special branches resulted in duplicate CI job runs) The container stage jobs can be triggered manually from the GitLab UI (and maybe also via the GitLab API, for people who'd like to automate this? I haven't looked into that). The build/test stage jobs run automatically once all their dependencies have passed. As an example, in order to run one of the "piglit-*" test jobs, one has to manually trigger the "x86_build" and "x86_test" jobs. The pipelines created for merge requests still run all jobs by default as before. The main motivation for these changes is to avoid wasting CI runner resources. In that same spirit, please also cancel any unneeded build/test jobs. This can be done already before those jobs start running, e.g. while the container stage jobs run. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
