Skip to content

fix: harden DEB NUTs against transient server-side lock errors - #1631

Open
WillieRuemmele wants to merge 1 commit into
mainfrom
wr/fixNut
Open

fix: harden DEB NUTs against transient server-side lock errors#1631
WillieRuemmele wants to merge 1 commit into
mainfrom
wr/fixNut

Conversation

@WillieRuemmele

Copy link
Copy Markdown
Contributor

Summary

  • Add deployWithRetry helper that retries deploy commands (up to 3 times with 15s/30s/45s backoff) when the only failures are transient "unable to obtain exclusive access to this record" server-side errors
  • Update all DEB NUT files (metadata, manifest, sourcepath, tracking, mpd) to use the retry helper for deploy commands
  • Non-transient deploy failures still fail immediately without retry

[skip-validate-pr]

Test plan

  • DEB NUTs pass in CI without intermittent lock-related failures
  • Non-transient deploy failures are still caught and reported immediately

Add deployWithRetry helper that retries deploy commands when the only
failures are transient "unable to obtain exclusive access" errors from
the Salesforce server. This addresses intermittent CI failures caused
by org-level record locking during consecutive DEB deploys.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant