Workflow visualization does not represent the workflow in a complex branching scenario

workflow
#1

Hi there,

I got a not so simple workflow:

workflows:
  my-workflow:
    jobs:
      - maven-test
      - approve-maven-pitest:
          type: approval
          requires:
            - maven-test
      - maven-pitest:
          requires:
            - approve-maven-pitest
      - maven-build-production:
          filters:
            branches:
              only: master
      - validate-terraform
      - stage-deploy:
          requires:
            - maven-build-production
            - maven-test
            - validate-terraform
      - stage2-deploy:
          requires:
            - maven-build-production
            - maven-test
            - validate-terraform
      - approve-production-deploy:
          type: approval
          requires:
            - stage-deploy
            - stage1-deploy
      - production-deploy:
          requires:
            - approve-prod-deploy

which gets visualized like this (see attached image).

In my opinion, this visualization is at least … confusing.
There is: maven-pitest requires approve-maven-pitest requires maven-test.
From the visualization, I do suggest, that approve-maven-pitest requires maven-test, maven-build-producation and validate-terraform. I do suggest, that approve-producation-deploy requires approve-maven-pitest (which is not the case).

0 Likes

#2

I completely agree. Can you please attach that image to https://ideas.circleci.com/ideas/CCI-I-850 and comment as need to clarify?

Sorry for how messy that feature request looks, I’ve let product know to take a look and clean it up.

0 Likes

#3

I have added a comment at https://ideas.circleci.com/ideas/CCI-I-850

1 Like

closed #4

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

0 Likes