Closed noxfate closed 3 weeks ago
This was due to jreleaser use maven central Publish API (ref), which is async operation while maven central takes some time to change statuses of the component from VALIDATING -> VALIDATE -> PUBLISHING -> PUBLISHED -> waiting period -> Appear in Maven Central.
We can work around by force exit code in jreleaser full-release
and then add scripts to check the deployment by using publisher API as well.
Details
jreleaser full-release steps on CI timeout and fail the 61 attempts when publish to maven central. This makes the CI fail, but actually the artifacts already deployed.
Expected
CI should reflects status of the artifacts deployment and release process correctly.
Like this example GH Runs: https://github.com/agoda-com/java-local-metrics/actions/runs/10810725596 Maven Central: https://central.sonatype.com/artifact/io.agodadev/testmetrics