Repository navigation
Add full and failed-job Azure DevOps build retries - #53
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Tiger can inspect pipeline failures but could not retry them. This adds a non-interactive retry command for both full reruns and failed-job retries.
tiger azdo retry <build-id>queues a new run using the original pipeline definition, branch, commit, and build/template parameters.tiger azdo retry <build-id> --failed-onlyuses Azure DevOps' retry API to retry failed jobs in the existing run. Eligibility and dependency handling remain server-controlled; errors do not fall back to a full rerun.Both modes accept
--organd--projectand return the resulting build as structured JSON. The HTTP rate-limit retry handler now preserves request bodies and headers so POST/PATCH requests remain intact after a 429 response. README and CLI skill documentation describe the new command.Validation:
dotnet test --nologopassed all 276 tests, including new coverage for request payloads, complete JSON responses, error propagation, cancellation, invalid input, and rate-limit retries. Command help was also verified. No live pipeline was retried.