hudson + build-number-plugin can't find svn
Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) 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:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 678) ... 28 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org .apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java: 59) at org.codehaus.mojo.build.BuildMojo.info(BuildMojo.java:526) at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:494) ... 32 more Caused by: org.apache.maven.scm.ScmException: Error while executing command. at org .codehaus .mojo.build.SvnInfoCommand.executeInfoCommand(SvnInfoCommand.java:102) at org .codehaus.mojo.build.SvnInfoCommand.executeCommand(SvnInfoCommand.java: 151) at org .apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java: 55) ... 34 more Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while executing process. at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java: 697) at org .codehaus .mojo.build.SvnInfoCommand.executeInfoCommand(SvnInfoCommand.java:80) ... 36 more Caused by: java.io.IOException: Cannot run program svn (in directory
RE: hudson + build-number-plugin can't find svn
I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the error. Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) 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:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 678) ... 28 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org .apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java: 59) at org.codehaus.mojo.build.BuildMojo.info(BuildMojo.java:526) at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:494) ... 32 more Caused by: org.apache.maven.scm.ScmException: Error while executing command. at org .codehaus
Re: hudson + build-number-plugin can't find svn
On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the error. Interesting. Makes sense. Our /usr/local/bin/svn is 1.6.3 though. Any suggestions on what to do? Thanks Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) 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:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: 182) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 678) ... 28 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org .apache .maven.scm.command.AbstractCommand.execute(AbstractCommand.java: 59) at org.codehaus.mojo.build.BuildMojo.info(BuildMojo.java:526) at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:494) ... 32 more Caused by: org.apache.maven.scm.ScmException
RE: hudson + build-number-plugin can't find svn
you need to downgrade to 1.5.x to match hudsons version. I just installed 1.5.x client on the Hudson box...you basically have to match the Hudson internal svn version. Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 9:54 PM To: Maven Users List Subject: Re: hudson + build-number-plugin can't find svn On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the error. Interesting. Makes sense. Our /usr/local/bin/svn is 1.6.3 though. Any suggestions on what to do? Thanks Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) 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:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: 182) at org .apache .maven .lifecycle
Re: hudson + build-number-plugin can't find svn
On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. Actually we just checked and it's using svnkit-1.3-hudson. SVNKit1.3 is compatible with svn 1.6 AFAIK. So if your /usr/local/svn is 1.4 then you will get the error. Again our /usr/local/bin/svn is 1.6.3 So any other suggestions? Perhaps it's really not finding it on the path? Can it be configured? Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) 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:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: 182) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 678) ... 28 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org .apache .maven.scm.command.AbstractCommand.execute(AbstractCommand.java: 59) at org.codehaus.mojo.build.BuildMojo.info(BuildMojo.java:526
RE: hudson + build-number-plugin can't find svn
Sorry, I'm looking at the stack trace, it appears the svn executable is not found. How are you launching Hudson? Make sure the startup script that launches Hudson has /usr/local/bin in its PATH. Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 9:54 PM To: Maven Users List Subject: Re: hudson + build-number-plugin can't find svn On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the error. Interesting. Makes sense. Our /usr/local/bin/svn is 1.6.3 though. Any suggestions on what to do? Thanks Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) 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:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: 182) at org .apache .maven .lifecycle
Re: hudson + build-number-plugin can't find svn
On 16/07/2009, at 1:11 PM, Mohan KR wrote: Sorry, I'm looking at the stack trace, it appears the svn executable is not found. How are you launching Hudson? Make sure the startup script that launches Hudson has /usr/local/bin in its PATH. it was already on the path -- but to be sure we added it again PATH= $PATH:/usr/local/bin. I'm now using the maven-antrun-plugin to print out the env.PATH and sure enough it's there twice - but it seems to work for now :-/ It'll probably fail again tomorrow... we'll see. Cheers. -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 9:54 PM To: Maven Users List Subject: Re: hudson + build-number-plugin can't find svn On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the error. Interesting. Makes sense. Our /usr/local/bin/svn is 1.6.3 though. Any suggestions on what to do? Thanks Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) 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:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377
