Problems with `needs:`
Summary
I have a monorepo with a few dozens of projects. So I decided to use the new DAG feature. I configured needs: where needed and created a new merge request.
-
Most of the jobs were run as expected however one of the jobs from the 3rd stage which was dependent from a job from the 1st stage wasn't run.
The 3rd and 4th stages of the pipeline were marked as pending.
The job's page stated that one of the needed jobs hadn't been run.
Cancelling and resuming that job didn't change anything. However rerunning the needed job made the dependent job run. -
The next commit in this merge request made one of the jobs from the 2nd stage fail. The dependent job from the 3rd stage was skipped as expected. But the job from the 4th stage dependent from that job from the 3rd stage was run and failed.
Rerunning needed job from the 2nd stage made the dependent job from the 3rd stage also rerun but not the dependent job from the 4th stage.
What is the current bug behavior?
- Sometimes jobs with
needs:hang. - Jobs dependent from the skipped job may run.
What is the expected correct behavior?
- Jobs with all of the needs fulfilled should be run
- Jobs dependent from the skipped job should be skipped