RFE: CI jobs should wait for downstream pipeline and reflect its state

Problem to solve

When starting a downstream build by using the ${CI_API_V4_URL}/projects/.../trigger/pipeline API, the triggering job should not complete until the downstream pipeline has been finished and should reflect its state.

Atm, such jobs are finished immediately and do not see when downstream fails. This renders e.g. the "pipeline must succeed" policy in merge requests useless.

There is no viable workaround for this problem. Active waiting withing the triggering job does not work because it blocks a builder. This might be ok for big companies with a large builder farm. But especially single developers have only a limited number of builders so the whole system might deadlock very easily.

Intended users

Developer

Further details

Downstream builds are common when working with git submodules; e.g. when a submodule is updated, trigger a build in to toplevel project and check whether updated submodule works.

Proposal

Wait for downstream pipeline and reflect its state

Permissions and Security

Documentation

Availability & Testing

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

What is the type of buyer?

single developer who wants to tests projects consisting of multiple repositories.

Links / references