Hudson dryRun作業從2.2.0升級到2.2.1後中斷

我剛剛將我們的Hudson從2.2.0升級到2.2.1，以修復電子郵件中的已知錯誤。這樣做導致了一些問題，尤其是在dryRun版本中。升級後，所有dryRun作業都失敗。Hudson dryRun作業從2.2.0升級到2.2.1後中斷

我不知道發生了什麼事，但導致一個svn版本衝突：

svn: The path '.' appears to be part of a Subversion 1.7 or greater 
working copy. Please upgrade your Subversion client to use this 
working copy.

我們有幾個建立以DRYRUN釋放：準備

clean -e release:clean release:prepare -DdryRun=true

哈德森的Maven（傳統）插件 - > 2.2.1
Hudson Maven3插件 - > 2.2.0
Hudson subversio n插件 - > 2.3.2

似乎文件正確下載，但「檢查修改」步驟似乎沒有必要。

Maven的輸出：

[INFO] Verifying that there are no local modifications... 
[INFO] Executing: /bin/sh -c cd /var/lib/hudson/jobs/anonymousName-app-svn-dryRun-release/workspace/app && svn --non-interactive status 
[INFO] Working directory: /var/lib/hudson/jobs/anonymousName-app-svn-dryRun-release/workspace/app 
[INFO] ------------------------------------------------------------------------ 
[ERROR] BUILD FAILURE 
[INFO] ------------------------------------------------------------------------ 
[INFO] Unable to check for local modifications 
Provider message: 
The svn command failed. 
Command output: 
svn: The path '.' appears to be part of a Subversion 1.7 or greater 
working copy. Please upgrade your Subversion client to use this 
working copy. 

[INFO] ------------------------------------------------------------------------ 
[INFO] Trace 
org.apache.maven.BuildFailureException: Unable to check for local modifications 
Provider message: 
The svn command failed. 
Command output: 
svn: The path '.' appears to be part of a Subversion 1.7 or greater 
working copy. Please upgrade your Subversion client to use this 
working copy. 

     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:48) 
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
     at java.lang.reflect.Method.invoke(Method.java:600) 
     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:173) 
     at hudson.maven.MavenBuilder.call(MavenBuilder.java:164) 
     at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:917) 
     at hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:848) 
     at hudson.remoting.UserRequest.perform(UserRequest.java:114) 
     at hudson.remoting.UserRequest.perform(UserRequest.java:48) 
     at hudson.remoting.Request$2.run(Request.java:283) 
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:453) 
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:315) 
     at java.util.concurrent.FutureTask.run(FutureTask.java:150) 
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:898) 
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:920) 
     at java.lang.Thread.run(Thread.java:736) 
Caused by: org.apache.maven.plugin.MojoFailureException: Unable to check for local modifications 
Provider message: 
The svn command failed. 
Command output: 
svn: The path '.' appears to be part of a Subversion 1.7 or greater 
working copy. Please upgrade your Subversion client to use this 
working copy. 

     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: Thu Jun 14 12:56:15 CEST 2012 
[INFO] Final Memory: 25M/63M

來源

2012-06-14 Vargen

看起來像新的Hudson以1.7格式檢查你的工作副本，但Maven使用的本地客戶端是1.6。轉到'http：// /configure' - >搜索'Subversion Workspace Version'並查看它的含義。 –

在version 2.2.1，哈德森升級在於SVNKit 1.7，導致Subversion工作拷貝使用非向後兼容1.7格式。

Maven release-plugin從路徑調用SCM提供程序Subversion。您的命令行中可能安裝了Subversion 1.6或更早的版本。

一種可能的解決方案是將您的命令行Subversion安裝升級到版本1.7。

來源

2012-06-16 08:21:05 user1460339

Hudson dryRun作業從2.2.0升級到2.2.1後中斷

回答

相關問題