diff options
author | Vincent Ambo <mail@tazj.in> | 2021-11-25T09·58+0300 |
---|---|---|
committer | Vincent Ambo <mail@tazj.in> | 2021-11-29T20·38+0300 |
commit | 6edfdd0773264b058736a8fb3887050d48a06c67 (patch) | |
tree | c4ced0382a57e284df33c585489e986d602967a7 /overrides | |
parent | 8de6c07153d59c6fce9c1ed0eb7d8d2ad9b1d70c (diff) |
refactor(ops/pipelines): Query build status from Buildkite API r/3116
Instead of manually tracking the build status through Buildkite metadata, use the Buildkite GraphQL API in the `:duck:` build step (i.e. the one that determines the status of the entire pipeline to be reported back to Gerrit) to fetch the number of failed jobs. This way we have less manual state accounting in the pipeline. The downside is that the GraphQL query embedded here is a little hard to read. Notes: * This needs an access token for Buildkite. We already have one for besadii which is also run by the agents, so I've given it GraphQL permissions and reused it. * I almost introduced a very rare bug here: My initial intuition was to simply `exit $FAILED_JOBS` - in the extremely rare case where `$FAILED_JOBS % 256 = 0` this would mean we would ... fail to fail the build :) Change-Id: I61976b11b591d722494d3010a362b544efe2cb25
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions