Jenkins和maven buildnumber插件

我使用的是1.0-beta-4版。这在从Subversion签出的项目上运行良好，但在Jenkins中失败

我认为这个问题是由于Jenkins以某种方式删除了

.svn

文件夹造成的

我想错了。以下是我得到的错误：

maven builder waiting
mavenExecutionResult exceptions not empty
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4:create (default) on project swift-core: Cannot get the revision information from the scm repository : 
Error!
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
    at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
    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.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
    at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:146)
    at hudson.maven.Maven3Builder.call(Maven3Builder.java:124)
    at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
    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.MojoExecutionException: Cannot get the revision information from the scm repository : 
Error!
    at org.codehaus.mojo.build.CreateMojo.getRevision(CreateMojo.java:673)
    at org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:431)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
    ... 27 more
Caused by: org.apache.maven.scm.ScmException: Error!
    at org.codehaus.mojo.build.CreateMojo.checkResult(CreateMojo.java:753)
    at org.codehaus.mojo.build.CreateMojo.getRevision(CreateMojo.java:648)
    ... 30 more

我忽略了这一点：

Provider message:
The svn command failed.
Command output:
/bin/sh: svn: command not found

mojoFailed org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-4(default)

---

计算机上没有安装

svn

客户端，这才是真正的故障源。

错误消息表明生成计算机上没有安装命令

svn

。您可以使用

javasvn

作为此配置的实现：

   <plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>buildnumber-maven-plugin</artifactId>
    <version>1.0</version>
    <executions>
      <execution>
        <phase>validate</phase>
        <goals>
          <goal>create</goal>
        </goals>
      </execution>
    </executions>
    <configuration>
      <doCheck>true</doCheck>
      <doUpdate>true</doUpdate>
      <providerImplementations>
        <svn>javasvn</svn>
      </providerImplementations>          
    </configuration>
  </plugin>

org.codehaus.mojo

如果您需要Subversion的特定版本（我们仍在使用1.5），您也可以绑定到svnkit的特定版本：

    <dependency>
        <groupId>org.tmatesoft.svnkit</groupId>
        <artifactId>svnkit</artifactId>
        <version>1.2.3.5521</version>
    </dependency>


org.tmatesoft.svnkit
斯文基特
1.2.3.5521
詹金斯是如何获得代码的？它在做svn结账吗？您可以尝试浏览工作区以确保.svn文件夹在那里。此外，Jenkins控制台对失败的生成的一些输出可能有用。@ig0774谢谢，我是个白痴。缺少
.svn
可能指向
svn导出
，而不是
签出
。太棒了。我不知道您可以使用javasvn独立于目标机器上安装的SVN。