[
https://issues.jenkins-ci.org/browse/JENKINS-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163154#comment-163154
]
sogabe commented on JENKINS-13840:
----------------------------------
change outputDirectory not to be removed.
{code}
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>cobertura-maven-plugin</artifactId>
<version>2.1</version>
<configuration>
<formats>
<format>html</format>
<format>xml</format>
</formats>
<outputDirectory>not_target_dir/cobertura</outputDirectory> <!-- here
</configuration>
</plugin>
{code}
> Cobertura fails the build if post build action of clean is specified
> --------------------------------------------------------------------
>
> Key: JENKINS-13840
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13840
> Project: Jenkins
> Issue Type: Bug
> Components: cobertura
> Affects Versions: current
> Reporter: scooper4711
> Assignee: stephenconnolly
>
> We need to keep disk space usage to a minimum, so we run mvn clean *after*
> every build.
> Unfortunately, with the post-build steps available in jenkins, the mvn clean
> runs before the cobertura report gets a chance to collect its data. So it
> complains that it cannot find coverage.xml and fails the build.
> The workaround we have is to use the m2extra steps plugin (which was
> deprecated after jenkins introduced the pre and post build capability). The
> m2extra steps plugin runs after the cobertura plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
