Frontend: Trigger job pending status is unclear
Release notes
Problem to solve
Trigger jobs that use strategy:depend
appear in pending
status until the DSP either succeeds or fails.
Based on the docs the purpose of the strategy: depend
feature is to mirror the pipeline status from the triggered pipeline to the source trigger job by using strategy: depend.
In reality we're not mirroring the status of the DSP to the trigger job in the UI. Mirroring the status implies that the status will appear the same for the trigger job and the DSP. Instead the trigger job appears as pending
until the final status of the DSP is known.
- It's not clear why the trigger job is in
pending
, and whatpending
means. - It's not clear what the DSP status is, even though the trigger job is set up to mirror the DSP status.
Related issues
- Child pipelines with manual jobs are unintuitive with strategy: depend. Pipelines can easily get stuck in running state.
- Upstream Pipeline Fails When Child Trigger Pipeline Passes - (Trigger pipeline marked as cancelled)
- Trigger job with strategy depend shows green when child pipeline passes with warnings
Proposal
Show an on-hover popover for trigger jobs with additional info about status
As an MVC we should communicate in the UI why the trigger job is pending and strengthen the visual connection between the trigger job and the DSP.
- When hovering over the trigger job show a popover that communicates the trigger job status and explanation why it's pending. We can also add a link to the related DSP which will open the DSP page. The link in the popover is the same as when you click on the trigger job, it takes you to the DSP page.
- This popover will only show for trigger jobs with
strategy: depend
when the trigger job is in a pending state.
Intended users
Feature Usage Metrics
Measure the number of clicks on the "View DSP pipeline" in the trigger job popover. This will allow us to learn more about how our users navigate the pipeline graph. Do they click on the DSP in the popover vs. the trigger job itself vs the downstream pipeline card?
Further iterations
A separate issue has been created to consider changes to how we mirror the trigger job and DSP status. Continuously mirror the DSP status to the trigg... (#371008)
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.