Closed pavolloffay closed 5 years ago
It seems you have some open staging repositories in Nexus. As suggested in the error message, please login to Nexus, remove all staging repositories and try again. If occurred again, disable running tasks in parallel and try once more (of course purging staging repositories via UI again before that).
Somehow strange is that both tasks closeRepository
and releaseRepository
failed. They should not be executed in parallel. Can you provided a link to a Travis build (if available)?
I have found a Travis build in a referenced issue.
Attempt 51/51 failed. WrongNumberOfRepositories was thrown with message 'Wrong number of received repositories in state 'open'. Expected 1, received 8'. Giving up. Configure longer timeout if necessary.
Definitely remove open repositories from Nexus.
@szpak thanks for looking into it.
I run into two problems:
upload
created multiple staging repositories because it changed IP. the same issue is here https://github.com/researchgate/gradle-release/issues/244#issuecomment-372794864Changing the IP address during one Travis build sounds suspicious for me. Can you:
or
In the second scenario:
build
task + whotever you need.upload
and closeAndReleaseRepository
in not parallel mode?Of course remove old staging repositories from Nexus before.
@szpak I get one error when execute the command "gradle releaseRepository". The error message is as followings. _"Execution failed for task ':releaseRepository'.Wrong 'comdellisgsmi-1073' repository state 'closed' after transition (expected [released, notfound]). Possible staging rules violation. Check repository status using Nexus UI." Besides, the repository has been closed successfully. The lastest version: 0.11.0 of "gradle-nexus-staging-plugin" is used.
@yaolingling Closed (no more files can be added to that repo, prepared for release) is not the same as released (here, push to Maven Central public repo). Has the package visible in the Maven Central?
You can paste a link to public CI logs (if available).
@szpak, thanks for your reply. My issue has been resolved. The root cause of this issue is that the same version of jar can't be released to the nexus manager. Change the version of released jar.
@pavolloffay do you still have that problem?
I think it was still present
@pavolloffay Could you try to disable parallel tasks execution (which may potentially cause more than one staging repository) with -Dorg.gradle.parallel=false
for the ./gradlew upload
task on Travis?
We do not use parallel execution. I do not think this would make a difference.
closing in favor of #76
Yes, now I know that the issue affects also a single treat execution even for a single module.
Hi,
we are using this plugin and it seems that closing/releasing does not work.
Here is our configuration https://github.com/jaegertracing/jaeger-client-java/blob/master/build.gradle#L81