[
https://issues.jenkins-ci.org/browse/JENKINS-10236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162459#comment-162459
]
SCM/JIRA link daemon commented on JENKINS-10236:
------------------------------------------------
Code changed in jenkins
User: Seiji Sogabe
Path:
src/main/java/hudson/plugins/emma/EmmaPublisher.java
http://jenkins-ci.org/commit/emma-plugin/bcad7397b2f907fc611844cb26c8cc1a120dbf52
Log:
[FIXED JENKINS-10236]Emma plugin causes maven release job to fail
> Emma plugin causes maven release job to fail
> --------------------------------------------
>
> Key: JENKINS-10236
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10236
> Project: Jenkins
> Issue Type: Bug
> Components: emma
> Affects Versions: current
> Reporter: Paul Sideleau
> Assignee: sogabe
>
> Jenkins marks a maven release build as having failed when the job has been
> configured to use the emma reports plugin and the maven release build is
> configured to run -Dresume=false release:prepare release:perform. The emma
> plugin logs the following:
> Emma: no coverage files found in workspace. Was any report generated?
> Build step 'Record Emma coverage report' changed build result to FAILURE
> There should be a way to disable the emma plugin from running when doing a
> release, or do not have it fail the release build.
> A work around is to include emma:emma in the "Release goals and options" when
> configuring the job.
--
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
