Connector Improvement: Buildkite Connector should pull triggered pipelines for jobs
Completed
The current Buildkite connector does not map in the data about a triggered job when a job in a pipeline build triggers a build in a separate pipeline. This data is already available in the Buildkite REST API. The current data returned for a Job in the API looks like this, and I propose that this information about a triggered job could be flattened out onto the buildkite_job table schema currently in use by the connector:
{"id":"0192c5fd-9da8-42cb-9db0-aba7da3acbac","type":"trigger","name":"Triggered Pipeline","state":"passed","async":true,"step_key":"trigger-a-pipeline",
..."triggered_build":{"id":"0192c61a-1caa-4fad-bc51-bd72c593a393","number":49009,
...},"soft_failed":false}
-
Official comment
Hello Brett,
Thank you for raising a feature request for the Buildkite connector.
We’re happy to share that the fields you mentioned have already been shipped and are available under the BUILD and BUILD_JOB tables.
Thank you again for your valuable feedback - it helps shape our roadmap.
Best,
Sisan
Please sign in to leave a comment.
Comments
1 comment