ci: trigger continuation on tags (#8466)
When the config was wrapped in a continuation so that params could be dynamically generated, this broke tag workflows since there was no explicit tag filter anymore in config.yml. This attempts to fix that. I may have gotten this wrong, since this is intrinsically hard to test. We'll see next time we tag something.
Gus Eggert committed
Sep 28, 2021 at 12:25 UTC
731b4de91ccfa302aec8e34b854fc705fc0559a8
2 files changed
+14
-1
.circleci/config.yml
+14
@@ -2,6 +2,14 @@ version: 2.1
2
setup: true
3
orbs:
4
continuation: circleci/continuation@0.2.0
5
+
6
+aliases:
7
+ only-version-tags: &only-version-tags
8
+ tags:
9
+ only: /^v[0-9].*/
10
+ branches:
11
+ ignore: /.*/
12
+
13
jobs:
14
generate-params:
15
executor: continuation/default
@@ -35,3 +43,9 @@ workflows:
43
setup-workflow:
44
jobs:
45
- generate-params
46
+
47
+ # NOTE: CircleCI only builds tags if you explicitly filter for them.
48
+ setup-workflow-tag:
49
+ jobs:
50
+ - generate-params:
51
+ filters: *only-version-tags
.circleci/main.yml
-1
@@ -442,7 +442,6 @@ workflows:
442
# the bifrost-* branches are used for deploying code that hasn't hit master yet (e.g. for testing)
443
- /^bifrost-.*/
444
445
-
445
# NOTE: CircleCI only builds tags if you explicitly filter for them. That
446
# also means tag-based jobs can only depend on other tag-based jobs, so we
447
# use a separate workflow because every job needs to be tagged together.