Maven发布插件发布失败。 svn 检出失败

发布于 2024-10-02 20:07:20 字数 1216 浏览 0 评论 0原文

嗨,我正在尝试在 Hudson 上使用 Maven 发布插件。 构建成功,之后,当 hudson 尝试发布该项目时,它失败并出现以下错误。

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: CHECKOUT of '/svn/projects/!svn/ver/82706/some/path/buildconfig/configuration/pom.xml': authorization failed: Could not authenticate to server: rejected Basic challenge (http://xx.xxx.xx.xx)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 17 seconds
[INFO] Finished at: Thu Nov xx 12:25:31 CST xxxx
[INFO] Final Memory: 22M/88M
[INFO] ------------------------------------------------------------------------
channel stopped
Finished: FAILURE

我在这里缺少什么。我在 stackoverflow 上看过一些与此相关的文章。但是,它们与 CHECKOUT 无关。

我认为这是 SVN 的问题,因此,maven 无法继续。运行 hudson 的人可以在命令行上执行基本的 SVN 命令。

任何与此相关的帮助将不胜感激。

Hi I'm trying to use the maven release plug-in on Hudson.
The build succeeds and after then, when hudson tries to release the project, it fails with the following error.

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: CHECKOUT of '/svn/projects/!svn/ver/82706/some/path/buildconfig/configuration/pom.xml': authorization failed: Could not authenticate to server: rejected Basic challenge (http://xx.xxx.xx.xx)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 17 seconds
[INFO] Finished at: Thu Nov xx 12:25:31 CST xxxx
[INFO] Final Memory: 22M/88M
[INFO] ------------------------------------------------------------------------
channel stopped
Finished: FAILURE

what I'm missing here. I have seen a few articles related to this on stackoverflow.But, they are not related to CHECKOUT.

I think its a problem with SVN, and because of that, maven cannot proceed. The person running the hudson can do the basic SVN commands on the command line.

Any help related to this will be appreciated.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

jJeQQOZ5 2024-10-09 20:07:20

运行 hudson 的人可以在命令行上执行基本的 SVN 命令。

这是否也意味着用户 Hudson 正在运行(很可能是“hudson”)可以执行 svn 命令?如果没有,您可以通过执行 sudo su hudson - 然后尝试 mvn release:prepare/perform 命令来检查。

The person running the hudson can do the basic SVN commands on the command line.

Does that also mean that the user Hudson is running as (most probably "hudson") can perform the svn commands? If not, you could check that by performing a sudo su hudson - and then trying the mvn release:prepare/perform commands.

诗酒趁年少 2024-10-09 20:07:20

这个问题是通过要求拥有 hudson 进程的人进行发布来解决的。
那时效果很好。我们遇到的问题是 hudson 没有共享用户。安装它的人拥有它。

当我们迁移到新的 hudson 框时,我们必须创建一个专用的 hudson 用户。

This problem was solved by asking the person who owned the hudson process to do the release.
It worked fine then. The problem we have is there is no shared user for hudson. The person who installed it owns it.

When we move to the new hudson box, we have to create a dedicated hudson user.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文