Expose pipeline_id in the job_info part of CI Job payload
What does this MR do and why?
Expose pipeline_id in the job_info part of CI Job payload
While GitLab Runner doesn't need any CI Pipeline context for job execution -- on the Runner side every job is executed individually and without connection to any other job -- information about Pipeline ID may be useful for some analytics and logging. For example - we want to include information about job's pipeline within the billing event context.
This commit exposes the ID in the payload, making it possible for GitLab Runner to consume it.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.