Repository navigation
Add build-wide retries for failed jobs - #1053
Merged
Merged
Conversation
Queue retries for an existing build with explicit confirmation and JSON, YAML, or text receipts. Validate targets before writing and report asynchronous acceptance without implying successful completion.
Keep annotation, step upload, and retry commands registered and documented together. Preserve configured quiet mode during retry pipeline discovery and cover it with terminal-backed tests.
buildsworth-bk-app
Bot
dismissed
their stale review
October 19, 2026 04:08
Superseded by a newer Buildsworth review.
mcncl
enabled auto-merge (squash)
October 19, 2026 04:08
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
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.
Description
Add
bk build retry-failed-jobsto queue retries in an existing build using the public REST endpoint, instead of retrying jobs individually.Changes
org/pipeline/number, or a Buildkite build URL, using the target organization's credentials.--states. Require confirmation unless--yesis supplied, and reject malformed or conflicting targets before retrying.202 Accepted. This does not wait for completion or establish that jobs are safe to rerun; retries are not limited to infrastructure failures and may repeat deployment side effects.Testing
env -u BUILDKITE_API_TOKEN go test ./... -count=1)gofumptgo vet ./...andgolangci-lint run --timeout 3mpass.