Add support for rules:needs:pipeline in the existing rules:needs feature

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

With GitLab v16.0 the team has introduced a new feature rules:needs (Documentation). But currently this does not support rules:needs where downstream pipeline needs a job from its parent pipeline, i.e., rules:needs:pipeline:job. Ideally rules:needs should support capabilities that needs currently have, such as needs:pipeline:job (Documentation).

The customer is looking for a feature where a job in a downstream pipeline should trigger when a given pipeline ID (another downstream pipeline) completes using the needs.

Zendesk Ticket (Internal URL): Link