停止发布MVN触发重复的Jenkins构建 [英] Stop mvn release triggering repeat Jenkins builds

问题描述

[通过maven-release-plugin发布，托管在Atlassian Stash上的Git repos触发了Jenkins中的构建管道.]

[Releasing via the maven-release-plugin, Git repos hosted on Atlassian Stash which triggers build pipeline in Jenkins.]

是否有一种方法可以停止发布以触发新的管道运行?发生这种情况是因为已发布的pom文件被提交回Stash.鉴于刚刚发生了构建(进入发布作业)，这完全没有必要，因为自上次构建以来所做的更改只是pom文件的版本号.

Is there a way to stop the release triggering a new run of the pipeline? This occurs because the released pom files are committed back to Stash. Given a build has just occurred (to get to the release job) this is entirely unnecessary as all that has changed from the last build is pom file version numbers.

推荐答案

Jenkins git插件可以配置为忽略某些提交消息，在您的情况下为[maven-release-plugin].

Jenkins git plugin can be configured to ignore certain commit messages, [maven-release-plugin] in your case.

请注意，帮助测试中用于忽略提交的示例存在一些问题，请尝试我的版本:^(?s)\[maven-release-plugin\].*

Note that the example in the help test for ignore commits has some problems, try my version: ^(?s)\[maven-release-plugin\].*

这篇关于停止发布MVN触发重复的Jenkins构建的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！