-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The task findSonatypeStagingRepository
is failing to match
#310
Comments
There might be the variety of reasons. Our, weekly running, e2e tests with that feature still works: publish-plugin/src/e2eTest/kotlin/io/github/gradlenexus/publishplugin/e2e/NexusPublishE2ETests.kt Lines 56 to 57 in c74635b
If you would like to get some help, please provide your project configuration and information from Nexus UI what is a description of existing staging repository(ies) at the moment of failure. |
The configuration for the project can be found at https://github.com/grails/grails-spring-security-cas/blob/4.0.x/build.gradle |
Thanks for the projects. It's strange, as there was a repository that should match:
I've just checked our e2e tests and "it worked":
I will take a closer look at the regex, maybe there is any problem with it 🤔 |
I think, I reproduced the problem in an automatic test. The problematic is leading ":". I will try handle also that case, but as a workaround, I propose to set "group" also in the root project or manually override the repository description:
where "..." can be your project name + current version. |
What's somehow "sad"", it seems that our e2e tests detected the problem a year ago (#200), but I thought, it is a problem with "unspecified" instead of a version... |
Define `group` for rootProject so that nexus-publish plugin correctly matches staging repository via Gradle task `findSonatypeStagingRepo`. This is suggested in gradle-nexus/publish-plugin#310.
Define `group` for rootProject so that nexus-publish plugin correctly matches staging repository via Gradle task `findSonatypeStagingRepo`. This is suggested in gradle-nexus/publish-plugin#310.
The text was updated successfully, but these errors were encountered: