gpt4 book ai didi

svn - Hudson “Perform Maven Release”无法在其他端口上提交svn + ssh

转载 作者:行者123 更新时间:2023-12-02 14:25:46 25 4
gpt4 key购买 nike

我们在非标准端口上设置了svn + ssh。

当Hudson询问我们时,我们在sd中添加了svn + ssh凭据。普通构建正常,没有任何问题:

Started by user anonymous
Checking out svn+ssh://xxx:22222/usr/local/svn_repo/repo/project/trunk
A pom.xml
U .
At revision 485

但是,当我们尝试“执行Maven版本”(M2版本插件)时,Hudson会在提交版本更改之前失败:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
ssh: xxx:22222: Name or service not known
svn: Commit failed (details follow):
svn: Connection closed unexpectedly

[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Unable to commit files
Provider message:
The svn command failed.
Command output:
ssh: xxx:22222: Name or service not known
svn: Commit failed (details follow):
svn: Connection closed unexpectedly

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:165)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:165)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:750)
at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:694)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files
Provider message:
The svn command failed.
Command output:
ssh: xxx:22222: Name or service not known
svn: Commit failed (details follow):
svn: Connection closed unexpectedly

at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:190)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 28 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12 seconds
[INFO] Finished at: Wed Nov 24 14:41:20 CET 2010
[INFO] Final Memory: 11M/155M
[INFO] ------------------------------------------------------------------------
channel stopped
Finished: FAILURE

当我尝试列出计算机中的某些内容时,我具有相同的“名称或服务未知”:
mah@hudson:~$ svn list svn+ssh://xxx:22222/usr/local/svn_repo/repo/project/trunk
ssh: xxx:22222: Name or service not known
svn: Connection closed unexpectedly

为了使它起作用,我需要在subversion config中修改隧道部分。但是,为什么我不能与Hudson进行发布?

最佳答案

这似乎是一个标准的SVN Issue (1942)

它还指出有一个补丁。我不知道该修补程序是否可以合并到Hudson中,但是您可以打开Bug/Feature Request

标准的,并且可能是最简单的解决方法是define an host alias

关于svn - Hudson “Perform Maven Release”无法在其他端口上提交svn + ssh,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/4267754/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com