Closed nullobject closed 5 years ago
@nullobject 👋 blast from the past!
I just wanted to give you a heads up that I shipped this! 🚀
BUILDKITE_TRIGGERED_FROM_BUILD_ID="da52eca0-a2a6-433c-8109-068a8f4b6e97"
BUILDKITE_TRIGGERED_FROM_BUILD_NUMBER="38"
BUILDKITE_TRIGGERED_FROM_BUILD_PIPELINE_SLUG="parent-pipeline-slug"
These are now available in builds created from other pipelines (not URL I'm afraid) but you should be able to reconstruct it using the new variables.
@keithpitt Ooh, very nice 👍
When I trigger another pipeline from a build, it would be nice if some of the environment vars from the parent build were automatically provided to the child build.
For example:
BUILDKITE_PARENT_BUILD_ID
BUILDKITE_PARENT_BUILD_NUMBER
BUILDKITE_PARENT_BUILD_URL
BUILDKITE_PARENT_PIPELINE_SLUG
Currently I am manually mapping these environment vars manually every time I trigger my "docker-deploy" build pipeline: