Jenkins maven发布subversion副本失败

时间:2016-10-14 06:09:41

标签: jenkins maven-release-plugin

从Jenkins发布Java模块时,系统显示以下日志:

------------------------------------------------------------------------
[INFO] Building mypro 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-release-plugin:2.5.2:prepare (default-cli) @ mypro ---
...
[INFO] Executing: /bin/sh -c cd /home/jenkins/workspace/mypro && svn --username myuser --password '*****' --no-auth-cache --non-interactive copy --file /tmp/maven-scm-1889961268.commit --parents --revision 001 https://myhost/svn/repos/mypro/tags/myparent-1.0.1/mypro https://myhost/svn/repos/mypro/tags/mypro-1.0.0
...
[ERROR] svn: E160013: '/svn/rpos/!svn/rvr/001/mypro/tags/myparent-1.0.1/mypro' path not found

pom.xml定义是:

<groupId>myGroupId</groupId>
    <artifactId>mypro</artifactId>
    <version>1.0.0-SNAPSHOT</version>
    <packaging>jar</packaging>

    <parent>
        <groupId>myGroupId</groupId>
        <artifactId>myparent</artifactId>
        <version>1.0.1</version>
    </parent>

subversion存储库结构

|--myparent
   |--trunk
   |--branch
   |--tags
|--mypro
   |--trunk
   |--branch
   |--tags

是否可以在不同的项目中使用maven父功能?

有没有办法配置maven-release-plugin使用“/ mypro / trunk”而不是“/mypro/tags/myparent-1.0.1/mypro”作为subversion copy命令中的源路径?

由于

1 个答案:

答案 0 :(得分:0)

  

有没有办法配置maven-release-plugin来使用&#34; / mypro / trunk&#34;而不是&#34; /mypro/tags/myparent-1.0.1/mypro"作为subversion copy命令中的源路径?

确保您的相应Module POM配置为与SCM中相同的Parent POM

<强>参考#:

Maven SCM configuration