DAG job runs when needs aren't met
Summary
A job with needs will run if the needed jobs aren't run and the pipeline fails
Steps to reproduce
Have a job need another job, and have something earlier in the pipeline fail.
Example Project
https://gitlab.com/Tysmith17/gitlab-dag-example/
What is the current bug behavior?
jobA needs jobB and jobB never runs, jobA will run
What is the expected correct behavior?
jobA needs jobB and jobB never runs, jobA does't run
Relevant logs and/or screenshots
n/a
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
n/a
Results of GitLab application Check
n/a
Possible fixes
The only work around we've found is to not use DAG in steps that deploy.
Edited by Tyler Winters