Hi Team,

Today, when a main pipeline invokes a chained (child) pipeline using the Pipeline step, the entire child pipeline executes — there is no native mechanism to select or filter specific stages from the child pipeline at the time of invocation from the parent.

When combined with looping strategies (Matrix / Repeat), this limitation means every loop iteration executes all stages in the child pipeline, even when only a subset of stages is relevant for a given iteration.

Scenario: A main pipeline deploys to multiple environments using a Matrix loop. Each environment requires only a specific subset of stages in the child pipeline (e.g., dev needs Build + Deploy, prod needs Build + Deploy + SmokeTest + ApprovalGate).

Today: Two separate child pipelines must be maintained, or complex when conditions must be embedded in the child pipeline for every possible combination.

With this feature: A single child pipeline is maintained, and the main pipeline selects the relevant stages per matrix iteration: