Repository navigation
ci: stop the Central publish at validation and wait up to an hour for the release - #52
Merged
Merged
Conversation
… the release to appear Central validates a deployment (signatures, POMs, sources and javadoc) within seconds but then publishes it on its own schedule, which took 15.5 minutes for 1.10.1 and longer for 1.10.2. The publishing plugin waits a fixed 15 minutes for PUBLISHED, so the 1.10.2 release job failed although its deployment was valid. Publish now returns once the deployment is VALIDATED (a signing or POM problem still fails the job), and the verify step polls Maven Central every 30 seconds for up to 60 minutes, logging progress.
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.
Why the 1.10.2 release job failed
The job failed after
Sign and publishreportedDeployment validation timed out after 900s. Last known state: PUBLISHING. Signing was not the problem:ac619d82…) within seconds. Validation includes the signature, POM, sources and javadoc checks, so they passed.repo1.maven.org.publishToMavenCentral(validateDeployment = PUBLISHED)waits at most 15 minutes for that step, and the limit is fixed in the plugin. 1.10.1 squeaked through: it was PUBLISHING from 13:08:40 to 13:24:05, about 15.5 minutes. 1.10.2 took longer, so the job failed even though the deployment was valid.The first attempt of the 1.10.2 job had a separate, temporary problem: every dependency download from
repo1.maven.orgfailed at 18:03, and the Nexus deploy failed the same way at the same minute. The re-run downloaded everything.Change
build.gradle.kts: publish withDeploymentValidation.VALIDATED. The step returns once Central accepts the deployment, and a signing or POM problem still fails it.check_central_release.py --published: polls Central every 30 seconds for up to--wait-minutes(60 in the workflow) and logs progress. It previously gave up after about 2 minutes. When it times out, it names the missing files and points to the Central Portal deployments page.maven-central.yml: the verify step passes--wait-minutes 60, and the job timeout goes from 70 to 80 minutes.Tested
./gradlew -PcentralRelease helpconfigures the Central publishing setup without errors.