Skip to content

ci: stop the Central publish at validation and wait up to an hour for the release - #52

Merged
ericlmao merged 1 commit into
mainfrom
ci/central-validated-then-wait
Nov 19, 2026
Merged

ericlmao merged 1 commit into
mainfrom
ci/central-validated-then-wait

Conversation

@ericlmao

Copy link
Copy Markdown
Member

Why the 1.10.2 release job failed

The job failed after Sign and publish reported Deployment validation timed out after 900s. Last known state: PUBLISHING. Signing was not the problem:

  • Central validated the 1.10.2 deployment (ac619d82…) within seconds. Validation includes the signature, POM, sources and javadoc checks, so they passed.
  • The deployment then sat in PUBLISHING, which is Central's own step that copies a validated release to 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.org failed 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 with DeploymentValidation.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

  • I ran the script against Central with stub POMs:
    • 1.10.1: passes at once.
    • 1.10.2, while it was still publishing: waits, then names the 16 missing files.
  • ./gradlew -PcentralRelease help configures the Central publishing setup without errors.

… 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.
@ericlmao
ericlmao merged commit 87eecc6 into main Nov 19, 2026
6 checks passed
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