Include Child Pipelines in DAG Visualization
Problem to solve
As a user of downstream pipelines, I am unable to benefit from the DAG Visualization efforts as the DAG Visualizations do not support visualizing multiple pipelines together.
This is aimed to address Parent/Child Pipelines (including Dynamic Pipelines) given that they never receive a Pipeline in the Pipelines list view of a project.
This is not dealing with Multi-Project Pipelines as those pipelines will show a pipeline for the downstream in the Pipelines list view of a project.
Intended users
User experience goal
Users of downstream pipelines would receive an immense amount of value from these visualizations due to the problems that exist from seeing connections between upstream and downstream pipelines.
Proposal
Find a way to implement DAG Visualizations even when needs: is not at play.
Further details
This issue is part of a more comprehensive solution detailed in &3156 (closed). Visibility of the Parent/Child pipeline relationships within the pipeline view is important for developers to have a good experience and be empowered to fix problems in this type of compliance workflow. This visualization should inform developers about failures in the pipeline regardless if they're locally defined or external to the project so an organization can maintain separation of duties without completely blocking developer velocity.
Types of Downstream Pipelines
-
Parent/Child Pipelines (including Dynamic): Using
trigger:syntax - Multi-Project Pipelines: Using Trigger Token, Personal Access Token, CI_JOB_TOKEN, Pipeline Subscriptions
Here's an example of a pipeline that the downstream pipeline is kicked off from the run ci job although there's no indication where the downstream job came from.
Before the child pipeline runs:
CURRENT During the child pipeline runs:
PROPOSED during the child pipeline runs (pretend run ci job looks paused):
