[gimp] gitlab-ci: store flatpak-build output into a log file.

[Jehan <jehanp src gnome org>]

commit eeb7b6315a1799118b951d2d034283902cda19e7
Author: Jehan <jehan girinstud io>
Date:   Wed May 26 20:28:47 2021 +0200

    gitlab-ci: store flatpak-build output into a log file.
    
    Without this, the flatpak build is just too long and Gitlab CI just
    stops logging it. So we end up with a log saying the quite useless (at
    the end):
    
    > Job's log exceeded limit of 16777216 bytes.
    > Job execution will continue but no more output will be collected.
    
    We don't even reach babl/GEGL/GIMP builds, which are the most important.
    With this little trick, I am redirecting output to a log file and simply
    including said log into the artifacts, hence allowing to debug the full
    build.

 .gitlab-ci.yml | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)
---
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 69eaf7f3f3..57ab61fe78 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -565,7 +565,23 @@ flatpak:
     FLATPAK_MODULE: "gimp"
     APP_ID: "org.gimp.GIMP"
     BUNDLE: "gimp-git.flatpak"
-
+  before_script:
+    # Our script is too long for Gitlab and ends up with:
+    # > Job's log exceeded limit of 16777216 bytes.
+    # > Job execution will continue but no more output will be collected.
+    # To make debugging actually possible, let's save logs as a file.
+    - shopt -s expand_aliases
+    - flatpak-builder-wrapper() { flatpak-builder "$@" > flatpak-builder.log 2>&1; }
+    - alias flatpak-builder=flatpak-builder-wrapper
+  artifacts:
+    paths:
+      - flatpak-builder.log
+      # These are the same as flatpak_ci_initiative.yml as according to
+      # docs, key values are not merged but replaced.
+      - "${BUNDLE}"
+      - 'repo.tar'
+      - '.flatpak-builder/build/${FLATPAK_MODULE}/_flatpak_build/meson-logs/meson-log.txt'
+      - '.flatpak-builder/build/${FLATPAK_MODULE}/_flatpak_build/meson-logs/testlog.txt'
 
 cppcheck:
   rules: