Make jobs depends on the previous job regardless of artefact availability
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem
In order to prevent missing dependency error states/scenarios from even happening in the first place, it would be wishful to be able to have more granularity for making jobs dependent on previous jobs in order to support DAG's.
Currently, you can make a job dependent on a previous job's status and availability of the artifact. It is however currently not possible to make the job depends on the previous job regardless if the artifact is available yes or no.
Usecase
This is for example required when transferring a CI configuration from a competitor product (e.a. Jenkins) towards GitLab-ci. There is a need in that case for more granularity (If this, then that logic) so flexible dependency statements make it possible to make things work with native GitLab primitives.
The current workaround consists of making the expiration time longer than necessary.
Further information
Follow up from #6144 (closed)