Raise the Central Portal upload timeout - #53
Merged
Conversation
The v1.0.1 publish failed with `Failed to stop service 'maven-central-build-service' > timeout` exactly 60s after the bundle upload started — SONATYPE_CONNECT_TIMEOUT_SECONDS defaults to 60 and is used as the OkHttp read timeout on the upload request. The upload had actually reached the Portal, so the deployment stayed alive and the retry was rejected with "Component with coordinate dev.nucleusframework:composewebview-jvm:1.0.1 is currently being published in another deployment". Give the Portal 10 minutes to answer instead.
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.
Follow-up to #52. The
v1.0.1publish job failed:exactly 60 s after the bundle upload started.
SONATYPE_CONNECT_TIMEOUT_SECONDSdefaults to 60 and the plugin uses it as the OkHttp read timeout onapi/v1/publisher/upload, so a slow Portal response fails the build even though the upload succeeded.That is what happened here — the deployment was live on the Portal, so re-running the job produced:
Giving the Portal 10 minutes to answer avoids both the spurious failure and the duplicate-deployment cleanup it causes. No behaviour change on a fast response.