Workflow not displaying and building all jobs with tags filter

Build Environment
1

Hi everyone,
I don’t know if I’m just blind to the obvious or if it’s a bug, so maybe anyone can help me.

I have one workflow that is working without problems:

test-commit:
    jobs:
      - lint-go:
          filters:
            tags:
              ignore: /^.*/
      - lint-api:
          filters:
            tags:
              ignore: /^.*/
      - check-gui:
          filters:
            tags:
              ignore: /^.*/
      - dep-gui:
          filters:
            tags:
              ignore: /^.*/
      - build-gui:
          requires:
            - lint-go
            - check-gui
            - dep-gui
      - test-1.10:
          requires:
            - lint-go
            - check-gui
            - dep-gui

The jobs build-gui and test-1.10 are correctly run only if lint-go, lint-api and check-gui passed. The UI of CircleCi also displays the dependency correctly. However as you can see this workflow shall not be executed if CircleCI was triggered by a tag. This also does work as intended.

Now for releasing my software I created another workflow that shall only be triggered when a tag is published. The triggering also works correctly, however the test-1.10 is not executed and is also not displayed in the GUI:

deploy-release:
    jobs:
      - lint-go:
          filters:
            branches:
              ignore: /.*/
            tags:
              only: /^v[0-9]+\.[0-9]+\.[0-9]+(-([a-zA-Z0-9]{8}))?$/
      - lint-api:
          filters:
            branches:
              ignore: /.*/
            tags:
              only: /^v[0-9]+\.[0-9]+\.[0-9]+(-([a-zA-Z0-9]{8}))?$/
      - check-gui:
          filters:
            branches:
              ignore: /.*/
            tags:
              only: /^v[0-9]+\.[0-9]+\.[0-9]+(-([a-zA-Z0-9]{8}))?$/
      - test-1.10:
          requires:
            - lint-go
            - check-gui
            - lint-api

CircleCI does also not display the dependency. It is as if the job was not considered for the workflow. Am I missing something here?
18

2

Ok I just found out that you need to add the tag filter to every job in the workflow. I expected it to behave as for the other workflow, meaning if the dependecy has a filter and is triggered then all the follow-up jobs without filters will be executed too.

3

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.