I define one job per each compiler version & build flavor that needs to be tested, like this: https://github.com/sociomantic-tsunami/turtle/blob/v8.x.x/.circleci/config.yml
It works pretty well as long as there is only one workflow stage and all builds run in parallel. However now I want to add additional post-test job and definition of the workflow because rather awkward:
workflows: version: 2 all: jobs: - test-1 - test-2 - test-3 - test-4 - test-5 - test-6 - post-test: requires: - test-1 - test-2 - test-3 - test-4 - test-5 - test-6 jobs: test-1: test-2: test-3: test-4: test-5: test-6:
All this long list of job names has to repeated again and again - once in job list, once inside a workflow and one time per every job in a next stage that depends on them. This isn’t nice to maintain at all.
I tried injecting this array in YAML anchors same as job object templates but looks like it is not supported by YAML parser used by CircleCI in any way.
Are there any better options to define this? Ideally I would simply want to define ordered test stages and not write individual test dependencies (like in GitLab CI or Travis CI).