Pipeline Retry does not satisfy 'needs' dependency

Summary

If you have a failed jobs which use needs, a retry of the pipeline will no start the job even if its depedencies are satisfied.

Steps to reproduce

  • created stages with needs
  • if one of them fails press retry for the pipeline
  • it's state gets reset but it does not start even if the job before did succeed

Example Project

https://gitlab.com/Flipez/broken-needs/pipelines/80192274

What is the current bug behavior?

the job 'has not been triggered yet'

What is the expected correct behavior?

the job should start

Edited Jul 15, 2020 by Jason Yavorsky
Assignee Loading
Time tracking Loading