Pipeline job dependency graph shows overlapping lines
Summary
The pipeline view, when grouping jobs by dependencies, still sort them by their respective stages and does not prevent dependency lines and job nodes from overlapping in misleading ways.
This bug has been reported on the GitLab forum in March 2022, but it appears the OP has yet to open an issue. The post can be found here.
Steps to reproduce
- Set up CI jobs in three stages. One in the first, one in the second, and one in the third. The latter two jobs needs to depend on the first job and only the first job.
- Run the pipeline.
- Check pipeline graph, grouped by dependencies.
Example Project
https://gitlab.com/atirutw/gitlab-ci-dependency-graph-bug-repro
What is the current bug behavior?
Take the following example configuration: .gitlab-ci.yml
In the attached configuration, the build stage takes place after the linting stage, but none of the jobs depends on linting stage jobs. The build jobs can and does start without waiting for lint jobs, but the dependency graph looks like this:
The graph suggests build jobs depending on lint jobs, but when you hover over them, it becomes apparent that they, in fact, do not depend on lint jobs. Instead, what is happening here is that the dependency lines of the build jobs are overlapping with the lint jobs when they should not be.
What is the expected correct behavior?
The job nodes in the graph should be sorted, left to right, by the order they run in according to their dependencies instead of being sorted by their stages.
Relevant logs and/or screenshots
See above.
Output of checks
This bug happens on GitLab.com
Possible fixes
N/A
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.
