Incorrect 'filters' key fails silently

Feedback & Bug Reports
,
1

Problem
I added a new job in my workflow. After pushing to my GH repository CircleCI started none of the jobs anymore. I found out there was a typo somewhere in my file. CircleCI did not give me this feedback

Expected behaviour
I would expect CircleCI to give me the feedback that an unrecognisable key had been found. Also I would expect CircleCI to run the other jobs, instead of running nothing at all.

Case
Turned out I made the mistake of typing the ‘filter’ instead of ‘filters’

- deploy-staging:
      requires:
        - build-test
      filter:
        branches:
          only:
            - /^staging_.*$/

had to be

- deploy-staging:
      requires:
        - build-test
      filters:
        branches:
          only:
            - /^staging_.*$/
1 Like
2

Hello

We are following up on old discuss articles and wanted to give an update.

Now if you include filter instead of filters you will see an error showing Unexpected argument(s): filter and when typing filter it will now autofill with filters.

We hope this will help in the future.

Kind Regards
Owen