Continuously mirror the DSP status to the trigger job status with strategy: depend

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 what pending means.
• It's not clear what the DSP status is, even though the trigger job is set up to mirror the DSP status.

In #363311 we're adding an on-hover popover for trigger jobs that are in a pending state due to their dependency on the downstream pipeline status, however it's not solving underlying problem of discrepancy between the trigger job and DSP statuses with strategy:depend.

WIP Proposal (needs further refinement)

When strategy: depend is used the trigger job status needs to continuously update to match the DSP status so the behavior in the UI matches the description in the docs (the trigger job should mirror the DSP status).

• As soon as the downstream is created, we should match the trigger status with the DSP status.
• While the trigger job is running and creating a DSP, it'll show up as pending, and a popover explaining the status should appear when hovering over the pending trigger job (see #363311)
• As the DSP and the trigger job change status to running and so on, the popover status information should change accordingly. (see #371008 (comment 1078170946) )

Open questions

• Could we get info about the DSP status more frequently so we can update the trigger job status to running once the DSP goes into running? Would this be a breaking change?
• We need to look at all the possible states of the trigger job and the DSP and map how the status should display.

Intended users

• Sasha (Software Developer)
• Priyanka (Platform Engineer)

Feature Usage Metrics

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.