Separate release repository task

[matejdro]

Currently, only way to trigger Maven central repository release is automatically, using automaticRelease = true. Is there any way to add an option to trigger this "manually"?

We would like to have a 2 step process:

1. Upload all libraries to Maven Central (this includes several different gradle projects, all calling publishAllPublicationsToMavenCentralRepository task)
2. Release staging repository on Maven Central all at once

The problem with having step 1 automatically release is that some projects could fail and some could succeed. This would result in a partially released maven central artifact. Ideally, if any of the uploads would fail in the step 1, the step 2 would not even be reached, so libraries would not actually be released.

[solrudev]

The problem with having step 1 automatically release is that some projects could fail and some could succeed. This would result in a partially released maven central artifact.

It's not true. Central Portal won't allow to publish an only partially verified deployment.

Edit: I assumed you meant artifact verification failure, not build failure. But in case of build failure, the whole build will terminate on failure, so nothing will be uploaded.

If automaticRelease is not set or is set to false, you can execute the task and it won't release a deployment automatically. Then you can go to Central Portal web interface and release it manually by clicking on the Publish button in the deployment info.

[matejdro]

Central Portal won't allow to publish an only partially verified deployment.

As far as I'm aware, this is only the case for the artifacts that are published together? If I publish multiple gradle projects, that have separate entries on the Central Portal, with the separate "Release/Close" buttons on the Central interface, there will not be any protection against this if one of the projects fail. And yes I'm talking about upload / plugin failure.

Then you can go to Central Portal web interface and release it manually by clicking on the Publish button in the deployment info

Yes, I'm aware of that, but I want that part done automatically via gradle task, just separate from the publish task.