Do not check CHANGES in pre-release pipelines

Since pre-release testing is usually carried out for branches in which
CHANGES entries are intentionally malformed to prevent entry numbering
conflicts down the road, do not run the "changes" GitLab CI job in
pipelines that are triggered by a parent pipeline (which can currently
only be a pre-release testing pipeline) to prevent triggering job
failures that would be meaningless anyway.

(cherry picked from commit 8c2503947f7ddea3437f89e8974690858736cb86)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index c2a2199339fdf7ca5089973e25c58a5d2e83240b..70edde5c74acbdb694a1671c30d50fc67c8ba716 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -531,6 +531,8 @@ misc:
 
 changes:
   <<: *precheck_job
+  except:
+    - pipelines
   script:
     - sh util/tabify-changes < CHANGES > CHANGES.tmp
     - diff -urNap CHANGES CHANGES.tmp