Feature request
Expose the execution status of child Pipelines so it can be consumed in Finally Tasks via $(tasks.<name>.status). Currently, execution status is not produced for PipelineTasks using pipelineRef or pipelineSpec.
This includes:
- Produce execution status (
Succeeded, Failed, etc.) for child Pipeline PipelineTasks
- Enable
$(tasks.<name>.status) references in Finally Tasks for child Pipeline PipelineTasks
- Update
docs/pipelines-in-pipelines.md known limitations section and documentation
See TEP-0056: Execution Status.
Use case
A parent Pipeline runs a security-scanning child Pipeline and sends a notification in a Finally Task with the outcome:
tasks:
- name: security-scans
pipelineRef:
name: security-scans
finally:
- name: notification
params:
- name: status
value: $(tasks.security-scans.status)
taskRef:
name: send-notification
Feature request
Expose the execution status of child
Pipelinesso it can be consumed inFinally Tasksvia$(tasks.<name>.status). Currently, execution status is not produced forPipelineTasksusingpipelineReforpipelineSpec.This includes:
Succeeded,Failed, etc.) for childPipelinePipelineTasks$(tasks.<name>.status)references inFinally Tasksfor childPipelinePipelineTasksdocs/pipelines-in-pipelines.mdknown limitations section and documentationSee TEP-0056: Execution Status.
Use case
A parent
Pipelineruns a security-scanning childPipelineand sends a notification in aFinally Taskwith the outcome: