Build is not following jobs requirements

Feedback & Bug Reports
1

Hello there,
for an unknown reason, a build that has been working for months is now executing all jobs in parallel instead of following the jobs requires: in workflow (IE: it starts with deploy-sd even if it requires publish-release, which itself requires build)

the config.yml

workflows:
  version: 2
  build-n-test:
    jobs:
      - build:
          context: org-global
      - run-tests:
          context: org-global
          requires:
            - build
      - publish-docker:
          context: org-global
          requires:
            - build
      - publish-release:
          context: org-global
          requires:
            - run-tests
            - publish-docker
          filters:
            branches:
              only:
                - master
      - deploy-sd:
          context: org-global
          requires:
            - publish-release
          filters:
            branches:
              only:
                - master
      - ha-approval:
          type: 'approval'
          requires:
            - deploy-sd
          filters:
            branches:
              only:
                - master
      - deploy-ha:
          context: org-global
          requires:
            - ha-approval
          filters:
            branches:
              only:
                - master

The current CI
image

link to the private failing build https://app.circleci.com/pipelines/github/iadvize/stats-service/6244/workflows/793ab9d4-f62d-4c57-87fe-e33d130e2f92

Any hint on that? There was no change on the config.yml since the last successful build.

Thanks!

2

The expected successful CI:

image
image2141Ă—123 15.2 KB

3

Hi @TidyMaze ,

Sorry to hear you were running into this problem. We identified the issue on our end, and pushed a fix. Could you confirm for me if the jobs are still not running in the correct order?

4

“Rerun workflow from start” doesn’t seem to be enough, I’ll try to make a commit and release another version of my app with a brand new build

5

a brand new build seems to be enough :slight_smile: I may have tried that before posting here ^^’

image
image2116Ă—112 11.4 KB

EDIT: I can confirm it’s working, thank you

6

@aaronclark

I’m still observing the same problem on https://app.circleci.com/pipelines/github/orange-cloudfoundry/osb-cmdb?filter=all with a build triggered today on march 24 with the following config

workflows:
  version: 2
  build-n-deploy:
    jobs:
      - build:
          filters:
            tags:
              ignore: /.*/
      - build_n_deploy:
          filters:
            branches:
              ignore: /.*/
            tags:
              only: /.*/
      - release_to_github:
          requires:
            - build_n_deploy
          filters:
            branches:
              ignore: /.*/
            tags:
              only: /.*/

where the release_to_github job runs before the build_n_deploy job that it requires
image

7

Thanks @aaronclark for the answer in the support ticket you provided: the fix took time for the circle fix to propagate to all customers, my new builds on March 25 were not affected anymore by the bug.