Description:

Currently, when a chained (child) pipeline is executed as part of a parent (gate) pipeline, rerun behavior does not propagate context to the child pipeline.

Problem

In a PR pipeline setup:

A parent “gate” pipeline triggers a child “PR checks” pipeline as a stage

If a PR check fails and the parent pipeline is rerun from a failed stage:

The child pipeline is re-executed

It does not recognize that it is part of a rerun context

All stages/jobs in the child pipeline run again, even those that previously succeeded

Expected Behavior

Child pipelines should be able to detect rerun context from the parent pipeline execution

Previously successful stages/jobs in the child pipeline should be skipped where applicable

Behavior should align with single-pipeline rerun optimization, where only failed or incomplete stages are re-executed