如何在Subversion的多模块Maven构建中触发单个模块的Jenkins构建? [英] How do I trigger a Jenkins build of a single module in a multi-module Maven build from Subversion?

问题描述

我在Jenkins中建立了一个大型的Maven多模块构建.它是为增量构建而设置的.

I have a big Maven multi-module build set up in my Jenkins. It is set up for incremental builds.

被触发时，它将解析所有POM并弄清楚它需要构建什么.

When triggered, it parses all the POMs and figures out what it needs to build.

当前已设置为在SCM更改时触发.

It is currently set up to trigger on SCM changes.

我想进行此构建，以便可以执行以下操作:

I would like to make this build so that I can do the following:

• 仍然手动启动它.当我这样做时，它的增量构建行为将像今天一样起作用.
• 从Subversion提交挂钩中触发构建.我想知道，如果我麻烦通过出色的说明，它不会导致构建过程不必要的长度来轮询SCM或执行提交钩子告诉它已更改的事实而使不必要的其他工作.

• Still start it manually. When I do this, its incremental build behavior would function as it does today.
• Trigger the build from a Subversion commit hook. I'd like to know that if I go to the trouble of setting up the commit hook via the excellent instructions that it will not cause the build to go to unnecessary lengths to poll the SCM or do other work that is rendered unnecessary by the fact that the commit hook is telling it what has changed.

之所以提到第二点，是因为从我的文档来看，这似乎只是戳开了一般的构建，然后让它做自己的事情. (我可能是错的.)我宁愿它告诉Jenkins到底发生了什么变化，而Jenkins只是知道"那些更改的存储库路径映射到哪些模块，因此Jenkins不必进行轮询或额外的pom.xml.进行分析以解决问题.

I mention the second point because from my looking at the documentation, this appears to simply poke the general build and let it do its thing. (I might be wrong.) I'd rather have it tell Jenkins exactly what has changed and have Jenkins just "know" what modules those changed repository paths map to, so that Jenkins doesn't have to do polling or extra pom.xml parsing to figure it out.

我已经准备好让经历过这场战争的人告诉我，看，就去设置Subversion提交钩子，这和您将要获得的效果一样好，但是我在问这个问题.如果有更好的食谱.

I am quite prepared to have someone who has been through this war to tell me, look, just go set up the Subversion commit hook and that's as good as you're going to get, but I'm asking this question in case there's a better recipe.

推荐答案

此工具不会但是在使用Maven 3构建时，显然在詹金斯(Jenkins)中已经存在.

This facility does not yet apparently exist in Jenkins when working with Maven 3 builds.

这篇关于如何在Subversion的多模块Maven构建中触发单个模块的Jenkins构建?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！