Empty dependencies array is not handle by extends

Summary

When declaring an empty "dependencies" array in a parent jobs to remove any dependencies to previous stages jobs, the child job doesn't inherit of this dependency removal.

Steps to reproduce

Example Project

Sample gitlab-ci.yml: https://gitlab.com/mgodlewski/gitlab_issue_extends_skip_empty_dependencies/blob/master/.gitlab-ci.yml

The corresponding pipeline

https://gitlab.com/mgodlewski/gitlab_issue_extends_skip_empty_dependencies/pipelines/100308954

The logs of jobs2 shows that dependencies are downloaded and present :/

Downloading artifacts for job1

What is the current bug behavior?

The job2 has dependencies to job1.

What is the expected correct behavior?

The job2 has NO dependencies to job1.

Possible fixes

Is this behaviour it's a feature, it should be documented.

But I'd rather prefer to see it as a bug because it's practical to remove dependencies in parent job definition.

Assignee Loading
Time tracking Loading