`closeAndReleaseRepository` fails because `publish` creates multiple staging repositories
See original GitHub issueI have a CI task that runs ./gradlew publish && ./gradlew closeAndReleaseRepository
.
This usually works, but I just ran into a CI error:
More than 1 matching staging repository found in account ***. You can can explicitly choose one by passing it as an option like this "./gradlew closeAndReleaseRepository --repository comexample-123". Available repositories are: com***-1119, com***-1120
I confirmed that there were two staging repositories created, and they were both created by the publish
task.
Issue Analytics
- State:
- Created a year ago
- Comments:25 (11 by maintainers)
Top Results From Across the Web
Fails to close/release · Issue #69 · Codearte/gradle-nexus ...
I run into two problems: when releasing on travis the upload created multiple staging repositories because it changed IP. the same issue is...
Read more >Issue with auto-generation of multiple staging repositories for ...
I am using the Gradle (1.12) Maven plugin to publish artifacts to Sonatype. I have a single build that generates and uploads all...
Read more >Gradle maven-publish / Sonatype creates multiple repositories ...
The signature is missing because it's in a different repository, that's exactly the problem I'm trying to solve. The files are put into ......
Read more >Gradle publishing plugins, a decision matrix | by Martin Bonnin
To mitigate this, the io.github.gradle-nexus.publish-plugin creates an explicit staging repository id where to upload your artifacts and ...
Read more >Reliable releasing to Maven Central from Travis using Gradle
It creates an explicit staging repository using the Nexus API and ... that publish (or publishToNexus ) and closeAndReleaseRepository has to ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just as an update, I’ve started working on explicitly creating a staging repository in the plugin that we can publish to explicitly.
Got the auto release working in one of my repos. Looks great, thanks!