Make staging repository operations retry on failure #17
Conversation
This file contains 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
MaciejG604
commented
Sep 21, 2023
MaciejG604
force-pushed
the
make-staging-repo-actions-retry
branch
from
6ec816c to
63d0a87
Compare
MaciejG604
force-pushed
the
make-staging-repo-actions-retry
branch
from
63d0a87 to
491991e
Compare
So that it still throws when something goes wrong, and users aren't surprised with the new behavior of createResponse
alexarchambault
approved these changes
Sep 27, 2023
|
LGTM |
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.
Publishing to sonatype sometimes fails with response HTTP 500
Unhandled: Staging repository is already transitioningThis happens right after the staging repository changes its status to 'closed' and a request is sent to promote it to
release.Adding a 'retry' mechanism may solve the issue.