CI "needs" limit can not be disabled
Summary
The CI/CD instance level setup allows to disable limits by setting them to "0".
When doing this for "Maximum number of DAG dependencies that a job can have", pipelines fail to run with
one job can only need 0 others, but you have listed 1. See needs keyword documentation for more details
Steps to reproduce
- Set "Maximum number of DAG dependencies that a job can have" to 0
- Try to run a pipeline with "needs:"