Customers have been asking for more flexibility when building dependency requirements between jobs. To date “requires” was based on the success of the required job. That is no longer the case. “Requires” now supports job status; success, failed, and canceled. So you can now build out complex dependency maps and fan in/out scenarios.
- When running complex fan-in/fan-out workflows, you may want to continue work even when there are test failures.
- When certain jobs fail or are canceled, you may want to execute cleanup jobs, or decide not to do a deployment.
Example Config
jobs:
- a
- b
- c:
requires:
- a canceled
- b:
- failed
- success
- d:
requires:
- a: #defaults to success
- b:
- failed
- success
Flexible requires, along with flexible when statements and expression based job filters, opens up more opportunities to optimize your pipelines for fast feedback and greater control of costs.
For more information on the feature visit the documentation.