本文介绍了Gradle上传失败,但仍部署到Nexus的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的gradle构建失败了uploadArchives任务;但是当我检查Nexus时,WAR和POM仍成功部署到了联系.谁能帮助我了解发生了什么事.

Hi my gradle build is failing in the uploadArchives task; but when I check Nexus, the WAR and POM are still deployed to nexus successfully. Can anyone help me understand what's going on.

26-Jul-2016 18:46:28    :compileGroovy UP-TO-DATE
26-Jul-2016 18:46:28    :buildProperties UP-TO-DATE
26-Jul-2016 18:46:28    :processResources UP-TO-DATE
26-Jul-2016 18:46:28    :classes UP-TO-DATE
26-Jul-2016 18:46:28    :compileTestJava UP-TO-DATE
26-Jul-2016 18:46:28    :compileTestGroovy UP-TO-DATE
26-Jul-2016 18:46:28    :compileGsonViews UP-TO-DATE
26-Jul-2016 18:46:36    :war
26-Jul-2016 18:46:44    Could not transfer artifact com.company.software:app-name:war:16.7.26-RELEASE from/to remote (https://www.company.com/nexus/repository/maven-releases/): Failed to transfer file: https://www.company.com/nexus/repository/maven-releases/com/company/software/app-name/16.7.26-RELEASE/app-name-16.7.26-RELEASE.war. Return code is: 400, ReasonPhrase: Repository does not allow updating assets: maven-releases.
26-Jul-2016 18:46:44    Could not transfer artifact com.company.software:app-name:pom:16.7.26-RELEASE from/to remote (https://www.company.com/nexus/repository/maven-releases/): Failed to transfer file: https://www.company.com/nexus/repository/maven-releases/com/company/software/app-name/16.7.26-RELEASE/app-name-16.7.26-RELEASE.pom. Return code is: 400, ReasonPhrase: Repository does not allow updating assets: maven-releases.
26-Jul-2016 18:46:44    :uploadArchives FAILED
26-Jul-2016 18:46:44
26-Jul-2016 18:46:44    FAILURE: Build failed with an exception.
26-Jul-2016 18:46:44
26-Jul-2016 18:46:44    * What went wrong:
26-Jul-2016 18:46:44    Execution failed for task ':uploadArchives'.
26-Jul-2016 18:46:44    > Could not publish configuration 'archives'
26-Jul-2016 18:46:44       > Failed to deploy artifacts: Could not transfer artifact com.company.software:app-name:war:16.7.26-RELEASE from/to remote (https://www.company.com/nexus/repository/maven-releases/): Failed to transfer file: https://www.company.com/nexus/repository/maven-releases/com/company/software/app-name/16.7.26-RELEASE/app-name-16.7.26-RELEASE.war. Return code is: 400, ReasonPhrase: Repository does not allow updating assets: maven-releases.
26-Jul-2016 18:46:44
26-Jul-2016 18:46:44    * Try:
26-Jul-2016 18:46:44    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
26-Jul-2016 18:46:44
26-Jul-2016 18:46:44    BUILD FAILED
26-Jul-2016 18:46:44
26-Jul-2016 18:46:44    Total time: 27.993 secs

推荐答案

我在将Maven版本推送到托管版本存储库时遇到了类似的错误:

I had a similar error pushing a maven release to a hosted release repository:

Error code 400, Repository does not allow updating assets: Releases -> [Help 1]

要修复此问题(在关系3中),我编辑了存储库,并将部署策略"值从禁用重新部署"切换为允许重新部署"

To fix it (in nexus 3) I edited the repository and switched the "Deployment policy" value from "Disable redeploy" to "Allow redeploy"

我的猜测是,它允许初始部署,但由于该政策,因此未能上传较新的版本.

My guess is that it allowed an initial deployment, but then failed to upload newer versions due to the policy.

这篇关于Gradle上传失败,但仍部署到Nexus的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

07-16 09:54
查看更多