Parent-Child Pipelines
Break complex workflows into reusable child pipelines triggered by a parent execution.
Note
Parent Pipeline: Contains and triggers multiple child pipelines.
Child Pipeline: Initiated by a parent workflow. Reusable across multiple parents.
Child Pipeline vs Parallel Processor
Child Pipeline
Runs one pipeline as a step. Parent success/failure affects it.
1
Parallel Processor
Runs multiple pipelines simultaneously in a single step.
5
💡 Ensure child pipelines are already configured and run successfully before linking.
Configure a Child Pipeline Step
Navigate to Pipelines → open or create a pipeline.
Enable the step, enter a name, choose tool as
Child Pipeline→ click Save.Under Step Settings, choose a child pipeline from the dropdown → click Save.
Click Start Pipeline. The child pipeline triggers automatically at this step.
Configure a Parallel Processor Step
Click Edit Workflow → click the pencil icon on the step.
Enable step, set name, choose tool as
Parallel Processor→ click Save.Click the gear icon → select up to 5 child pipelines from the Pipelines dropdown → click Save.
Click Start Pipeline. All linked child pipelines trigger in parallel.
Approvals for Parent-Child Pipelines
Approval dialogs auto-collect deployment artifacts from child pipelines. No need to navigate to external build logs.
Navigate to the pipeline execution awaiting approval → open the Approval step.
Verify step name and approval ID.
Review deployment artifacts: image names, tags, source pipelines, and target environments.
Enter comments (recorded in Pipeline Activity Logs).
Click Approve to proceed or Deny to stop.
Last updated

