Make pipeline graph information better depict inter pipeline connectivity

Problem to solve

We display the downstream pipeline having <project> - <pipeline-id>

image

With the introduction of child pipelines #16094 (closed) we are adding in additional node types. #25353 (closed) will introduce a visual update.

There might be an opportunity to review if the current view is actually effective at making the user understand inter pipeline connectivity.

Intended users

Further details

Proposal

Taken from #16094 (comment 254378770)

Do we need to use Child, Downstream, Upstream, Parent labels? Wouldn't it be clear from the project name whether it's a cross-project pipeline or same-project pipeline?

Imagine a pipeline on gitlab-org/gitlab project that shows the following pipelines in the downstream column:

  • gitlab • #86
  • gitlab • #87
  • workhorse • #205

That means that the first 2 will be child-pipelines while also creating a cross-project pipeline for Workhorse project.

What is still missing IMO is which job created the pipeline as it would add very useful visual context as well as visual reference to the bridge job. E.g. the same list with stage/job names:

  • test/docs ▶ gitlab • #86
  • test/unit ▶ gitlab • #87
  • build/workhorse ▶ workhorse • #205

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references