From 82906e5d5de8a294613c0ad1a360e3d8112567d4 Mon Sep 17 00:00:00 2001
From: Philip Withnall <withnall@endlessm.com>
Date: Wed, 12 Jun 2019 14:31:42 +0100
Subject: [PATCH] ci: Run scan-build in a different build directory
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The build artifacts from earlier jobs in the pipeline all use the
`_build` directory. When they are copied in to the scan-build job, they
are probably marked as read-only. This means that the `meson scan-build`
run can’t write to `_build/meson-logs/meson-log.txt` and fails.

Signed-off-by: Philip Withnall <withnall@endlessm.com>
---
 .gitlab-ci.yml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 9bff123ea..81fddc25f 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -255,13 +255,13 @@ scan-build:
             -Ddtrace=true
             -Dfam=true
             -Dinstalled_tests=true
-            _build
-    - ninja -C _build scan-build
+            _scan_build
+    - ninja -C _scan_build scan-build
   artifacts:
     name: "glib-${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}"
     when: always
     paths:
-      - "_build/meson-logs/scanbuild"
+      - "_scan_build/meson-logs/scanbuild"
 
 pages:
   stage: deploy