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.

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