DOCS-2704 / 27 / checkout resilience against concurrent-DNS-flake (master) - #4762
Merged
Conversation
…DOCS-2704) Same change smoke-tested and confirmed working on 25.10 (PR #4761, build #19 SUCCESS): skipDefaultCheckout() + an explicit Checkout stage serialized via lock('docs-checkout') (mirrors the existing docs1-deploy lock pattern), with a narrow retry (max 3 attempts, 10s backoff) that fires only on the diagnosed 'Could not resolve host: github.com' signature — any other exception fails immediately so a real problem isn't masked. timeout(5m) bounds worst-case queuing latency if many branches trigger together.
bugclerk
changed the title
Contributor
tonyriv3
added
the
Technical Writer Review (TR)
tonyriv3
approved these changes
Sep 2, 2026
Contributor
|
This PR has been merged and conversations have been locked. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Same change already smoke-tested and confirmed working on
25.10(#4761, build #19 SUCCESS — lock acquired/released cleanly, checkout+commit metadata correct, pipeline completed through Symlink).Root-caused an incident from the DOCS-2704 cleanup: merging cleanup PRs to several branches within minutes of each other caused
Docs Versioned Sitesto trigger concurrent builds, and simultaneous SCM checkouts on the shareddocbuilds02agent intermittently failed withCould not resolve host: github.com. Confirmed empirically — 3 branches triggered simultaneously gave mixed pass/fail on the same node; every branch went green when retried one at a time.skipDefaultCheckout()+ explicitCheckoutstage, serialized vialock('docs-checkout'), narrow retry (3 attempts, 10s backoff) only on the diagnosed DNS-failure signature,timeout(5m)to bound worst-case queuing.