publish-plugin VS gradle-play-publisher

To easily automate publishing later, you'll use the gradle-nexus/publish-plugin tool. This has to be added in your project level (root) build.gradle file as a dependency.

There is a remedy: Gradle Nexus Publish Plugin. This plugin automatically closes and releases OSSRH staging repositories whenever you publish something. To use it, remove the repositories section from the publishing plugin configuration of your build script (the one mentioning "OSSRH" in my example above) and add these lines to your build:

Yeah, the new plugin which combines both of these functionalities is wip https://github.com/gradle-nexus/publish-plugin . I assume this will get released soon.

Kinda. You can set up say a CI on circle ci, and on successful build and tests run it's gonna use this https://github.com/Triple-T/gradle-play-publisher to push to internal test track in play console. And that internal track is available to qa and if we get a green light we can elevate it to release manually

I'm using this Gradle plugin. Pretty easy to configure in your Gradle files and then just run the correct task.

It's https://github.com/Triple-T/gradle-play-publisher, it uses play store APIs, sure. But it's unrelated to the app code itself

There you go: https://github.com/Triple-T/gradle-play-publisher