Submit Your Ideas

We want to hear from you - vote for the features and improvements you'd most like to see, or submit your own ideas if you don't find them already listed.

Add new attribute to control execution order of workflow jobs without 'requires'

in our current configuration we have a workflow that:

1) builds the project
2) runs our unit tests
3) runs our dtests (distributed tests -- so we can test that particular C* features that can't be tested in a unit test)

with_dtests_jobs: &with_dtest_jobs
jobs:
- build
- unit_tests:
requires:
- build
- dtests-with-vnodes:
requires:
- build
- dtests-no-vnodes:
requires:
- build

ideally, there'd be another parameter instead of "requires" that allows the end user to control the execution order of a workflow but doesn't actually dictate that the "required" step ahead of it successfully completed

thinking a little more about this: maybe a new explicit keyword isn't required.... but instead circle should just respect the order in which the jobs were defined in the workflow.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 9 2018
  • Future consideration
  • Attach files