feat(stovepipe): add Buildkite and GitHub Actions BuildRunner backends#411
Closed
roychying wants to merge 7 commits into
Closed
Conversation
roychying
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
July 21, 2026 00:04
roychying
force-pushed
the
chenghan.ying/stovepipe-buildsignal-controller
branch
from
July 21, 2026 22:20
63562b5 to
be3d253
Compare
roychying
force-pushed
the
chenghan.ying/refactor-buildrunner-extension
branch
from
July 21, 2026 22:21
aed9544 to
9a77b28
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
platform/extension/buildrunner/{buildkite,githubactions}shared HTTP clients (CreateBuild/GetBuild/CancelBuildfor Buildkite;DispatchWorkflow/GetRun/CancelRunfor GitHub Actions), domain-agnostic and reusable by bothsubmitqueueandstovepipe.stovepipe/extension/buildrunner/{buildkite,githubactions}thin adapters wrapping those clients. Buildkite passes identity via env vars (STOVEPIPE_HEAD_URI/_BASE_URI/_QUEUE/_METADATA) and recovers metadata from Buildkite's echoed env vars; GitHub Actions passes identity viaworkflow_dispatchinputs and, since GitHub doesn't echo inputs back, returns the run's own status/outcome fields instead. Both map unrecognized backend states toBuildStatusUnknown(non-terminal) rather than guessing terminal.submitqueue/extension/buildrunner/{buildkite,githubactions}to consume the same new shared platform clients instead of owning their own HTTP logic.Test Plan
make build,make test- all greenIssue