我正在使用Jenkins
和Maven
来构建一些Java项目。此外,我正在使用Cobertura
进行覆盖率分析。因此,我设置了一个 Jenkins Maven 构建作业并配置了以下目标:
clean cobertura:cobertura
这对于覆盖率分析工作正常,但不生成 POM 中配置的任何 jar 输出。我认为是这样,因为Maven的目标package
不在Cobertura生命周期中。
为了获取jar文件,我尝试将其更改为
clean cobertura:cobertura install
这正在做这项工作,但遇到了另一个问题:从resources
到test
的每个目标都执行两次:(控制台输出如下所示(删除了详细信息行)
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ HelloWorld ---
[INFO] >>> cobertura-maven-plugin:2.7:cobertura (default-cli) > [cobertura]test @ HelloWorld >>>
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ HelloWorld ---
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ HelloWorld ---
[INFO] --- cobertura-maven-plugin:2.7:instrument (default-cli) @ HelloWorld ---
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ HelloWorld ---
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ HelloWorld ---
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ HelloWorld ---
[INFO] <<< cobertura-maven-plugin:2.7:cobertura (default-cli) < [cobertura]test @ HelloWorld <<<
[INFO] --- cobertura-maven-plugin:2.7:cobertura (default-cli) @ HelloWorld ---
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ HelloWorld ---
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ HelloWorld ---
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ HelloWorld ---
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ HelloWorld ---
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ HelloWorld ---
[INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ HelloWorld ---
[INFO] --- maven-install-plugin:2.4:install (default-install) @ HelloWorld ---
有没有办法使用install
使用阶段resources
的结果到cobertura
test
的结果?
换句话说,输出像
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ HelloWorld ---
[INFO] >>> cobertura-maven-plugin:2.7:cobertura (default-cli) > [cobertura]test @ HelloWorld >>>
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ HelloWorld ---
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ HelloWorld ---
[INFO] --- cobertura-maven-plugin:2.7:instrument (default-cli) @ HelloWorld ---
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ HelloWorld ---
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ HelloWorld ---
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ HelloWorld ---
[INFO] <<< cobertura-maven-plugin:2.7:cobertura (default-cli) < [cobertura]test @ HelloWorld <<<
[INFO] --- cobertura-maven-plugin:2.7:cobertura (default-cli) @ HelloWorld ---
[INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ HelloWorld ---
[INFO] --- maven-install-plugin:2.4:install (default-install) @ HelloWorld ---
附加信息:更改 POM 不是一种选择,因为它们不是由我管理的。
简短的回答:没有。通过一些反复试验,我终于找到了一个可以忍受的解决方案:
离开Maven的目标,比如
clean cobertura:cobertura
并添加执行 Maven 目标的构建后步骤
install -Dmaven.test.skip=true
这样测试就不会执行两次。 compile
和类似的被执行了两次,但这还不错,因为Cobertura已经编译了所有内容,迫使Maven跳过这一步。
注意:clean cobertura:cobertura install -Dmaven.test.skip=true
是不可能的,因为test.skip
开关对两个目标都有影响。