docs: better explanation of circleci opt-in to tags madness
Thanks to @Mr0grog Co-Authored-By: Rob Brackett <rob@robbrackett.com>
Oli Evans committed
Mar 6, 2020 at 09:37 UTC
e83862ae7c8bdd42e8182b6042d9b37f62e2bdc9
1 file changed
+3
-1
.circleci/config.yml
+3
-1
@@ -369,7 +369,9 @@ workflows:
369
- go-ipfs-http-client
370
- ipfs-webui
371
372
- # NOTE: You have to opt in to get circleci to trigger builds for a tat. As it is required that you set the tag filter to all dependent jobs, this is pulled out into a seperate workflow.
372
+ # NOTE: CircleCI only builds tags if you explicitly filter for them. That
373
+ # also means tag-based jobs can only depend on other tag-based jobs, so we
374
+ # use a separate workflow because every job needs to be tagged together.
375
# see: https://circleci.com/docs/2.0/workflows/#executing-workflows-for-a-git-tag
376
docker-on-tag:
377
jobs: