Retry file operations on access denied errors#1408
Merged
Merged
Conversation
This should improve resiliency in cloudbuilds where multiple top-level builds are executed in the same repo concurrently (naughty).
There was a problem hiding this comment.
Pull request overview
Improves resilience of file write/update operations by retrying on additional transient file-access failures that can occur when multiple builds operate concurrently in the same working directory.
Changes:
- Expand retry logic to treat both sharing violations and access-denied failures as transient (via
IsTransientFileAccessError). - Ensure the final retry attempt surfaces the exception (retry only while
retriesLeft > 1) and useThread.Sleepfor the backoff.
This was referenced Jul 8, 2026
Open
This was referenced Jul 13, 2026
Open
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.
This should improve resiliency in cloudbuilds where multiple top-level builds are executed in the same repo concurrently (naughty).