Add parent_{pipeline,project,job}_id to pipeline API for downstream pipelines (child, multi-project)
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
The pipeline API does not currently support linking downstream pipelines (child pipelines and multi-project pipelines) to their parent pipeline, parent job, or parent project. It does however support linking parent pipelines to their children, through the pipeline bridges endpoint.
Without this child -> parent link, parents must explicitly pass their IDs to their children as variables. If the parent IDs need to be validated in the child, the child needs to query the bridges endpoint for the parent pipeline and find itself.
Proposal
The pipeline API should include parent_pipeline_id, parent_project_id, and parent_job_id for all downstream pipelines (pipelines triggered by another - parent/child and multi-project).