If a Maven Publish times out, PyPi deployment is skipped

[triceo]

Publishing in Maven Central takes a while. This time, it took a very long time, and JReleaser timed out. This in turn caused the release job to fail, without deploying to PyPi.

But once the deployment to Maven Central is started, it cannot be taken back. Therefore the release will be published even though JReleaser failed. This leaves us in an inconsistent situation where the release is published on Maven Central, but not in PyPi.

[aalmiray]

FWIW you can change the default settings for delay and retries to give JReleaser a bit more space. As you noted, once the deployment has started the remote may continue and succeed even if the local build fails due to timeout, as once a deployment publication is triggered the tool simply waits for a status change.

[triceo]

Hello @aalmiray!

When we were using the previous configuration (Nexus), before migrating to the new Central publisher, we had an option to not close the release - requiring a later manual step, but avoiding this problem. Did I miss it in the docs, or is that no longer possible?

[aalmiray]

The MavenCentral publishers works in a different way than Nexus2. However, you can still use staged deployments https://jreleaser.org/guide/latest/reference/deploy/maven/maven-central.html#_staged_deployments

[triceo]

Thanks Andres, I'll look into it!