gitlab CI: don't run meson test on the scan-build job
authorPeter Hutterer <peter.hutterer@who-t.net>
Fri, 21 Feb 2020 00:37:56 +0000 (10:37 +1000)
committerPeter Hutterer <peter.hutterer@who-t.net>
Mon, 24 Feb 2020 01:53:21 +0000 (01:53 +0000)
commitdafb68f306b62ac483faf3b4c2ecb9cb021bc1b5
tree1fe0c6a8a963100da31964fb9a7f9637d247ca02
parent20cf83789df6563828f16fc938ccf05437d366c2
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>
.gitlab-ci.yml
.gitlab-ci/gitlab-ci.tmpl