Peter Hutterer dafb68f306 gitlab CI: don't run meson test on the scan-build job ... Unfortunate side-effect of this: scan-build would store the logs in the build dir, only for them to be immediately wiped by meson test. And that never generated the scan-build warnings. So this job was complaining about (minor) issues for a while, they just never made it to the GUI as CI failures. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>		2020-02-24 01:53:21 +00:00
..
check-commit.py	gitlab CI: add an explanatory comment why we're hardcoding master	2019-12-05 10:40:40 +10:00
generate-gitlab-ci.py	gitlab CI: use a separate variable for the template list	2020-02-20 13:39:32 +10:00
gitlab-ci.tmpl	gitlab CI: don't run meson test on the scan-build job	2020-02-24 01:53:21 +00:00
meson-build.sh	gitlab CI: run the meson script for the VMs as well	2019-11-28 14:36:00 +01:00
meson-junit-report.py	gitlab CI: add meson to junit script	2019-11-28 11:52:54 +01:00
ubuntu_install.sh	CI: use templates for Ubuntu	2019-04-01 04:11:20 +00:00