Question

我需要发布一个较旧的分支来满足不同团队的依赖关系。设置是通过Jenkins使用maven-release插件完成的。正如标题所示，一切顺利，直到它到达复制到标记阶段，而不是复制到分支，它复制主干并在尝试构建它时失败，因为主干设置为部署到不同的连接。

请帮助我几乎整整一天都在绞尽脑汁。

目前的詹金斯目标：

-X -DdryRun = $ {DRY_RUN_MODE} -DbranchName = release_1.243 -Dapp.svn.repo = $ {APP_SVN_REPO} clean release：prepare release：perform

当前配置：

<plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-deploy-plugin</artifactId>
                <version>2.8.2</version>
            </plugin>

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-release-plugin</artifactId>
                <version>2.5.3</version>
                <configuration>
                    <branchName>release_1.243</branchName>
                    <tagNameFormat>release_branch_@{project.version}</tagNameFormat>
                </configuration>
            </plugin>


            <scm>
        <connection>${project.svn.repo}/trunk</connection>
        <!-- Because we have a single-module SVN repo with a FLAT multi-module
            file structure, we need to point to this parent pom's folder in the developer
            connection, not the root (trunk) repo. -->
        <developerConnection>scm:svn:${project.svn.repo}/trunk/app-parent</developerConnection>
    </scm>

Answer 1

connection>${mach.svn.repo}/branches/release_1.243</connection>
        <!-- Because we have a single-module SVN repo with a FLAT multi-module
            file structure, we need to point to this parent pom's folder in the developer
            connection, not the root (trunk) repo. -->
        <developerConnection>scm:svn:${mach.svn.repo}/branches/release_1.243/efx-parent</developerConnection>

这解决了它，但是khmarbaise应该得到信任，即使我在阅读他的评论之前解决了它。

Maven Release Plugin Jenkins继续将Trunk复制到Tag而不是Branch

1 个答案: