Skip to content

Add upstream pipeline attributes to pipeline hooks

What does this MR do and why?

Adds some new fields to the data in Pipeline Hook events. These fields are useful info about the upstream pipeline, if it exists:

  • upstream project ID
  • project web_url
  • project full path with namespace prefix
  • upstream pipeline ID
  • bridge job ID

Screenshots or screen recordings

Currently looks like this:

:source_pipeline=>{:project=>{:id=>6, :web_url=>"http://localhost/namespace3/project3"}, :job_id=>12, :pipeline_id=>8}}

How to set up and validate locally

Just define a child pipeline or a multi-project pipeline and trigger it. The webhooks about it now contain these additional fields.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Marius Bobin

Merge request reports