fix: suppress re-running CI on tagged commits

Several tasks in the CI setup were allowed to run on tagged commits. This meant
that pushing a new tag would result in re-running CI on the tagged commit. This
was already confusing, but was compounded by these unrestricted tasks depending
on non-tag-only tasks. The result was that CI would stall and fail because
dependencies could not be satisfied.

To fix this we simply disallow all CI on a tag. This means that a tagged commit
that is not on any branch will not be tested. However, no one should be pushing
such a commit to the Graphviz repository. All tagged commits that are on a
branch will be tested via their SHA. This is not expected to cause any problems
as the Graphviz build system never checks the Git tag or whether a commit is
tagged at all.

Fixes #1901.

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 95121525d8b4ffe684d1d81605c53235e3a03ffa..dffcf73855a06c58d4cfa0ae198bd16217e699b3 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -182,6 +182,8 @@ portable-source:
             junit: ./report.xml
     tags:
         - windows
+    except:
+        - tags
 
 .test_template: &test_definition
     stage: test
@@ -193,6 +195,8 @@ portable-source:
     artifacts:
         reports:
             junit: ./report.xml
+    except:
+        - tags
 
 centos7-build:
     <<: *rpm_build_definition
@@ -379,6 +383,8 @@ meta-data:
     artifacts:
         paths:
             - configuration-*.html
+    except:
+        - tags
 
 ubuntu18-04-test:
     <<: *test_definition