[
https://issues.jenkins-ci.org/browse/JENKINS-12645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163317#comment-163317
]
acdha commented on JENKINS-12645:
---------------------------------
A common trigger for this is that the acceptable values for the directory name
are completely undocumented and not relative to the workspace. Using something
like {{{**/coverage}}} will work but simply {{{coverage}}} will not.
> Violations plugin reports its own failures as build failures
> ------------------------------------------------------------
>
> Key: JENKINS-12645
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12645
> Project: Jenkins
> Issue Type: Bug
> Components: violations
> Reporter: acdha
> Assignee: peterkittreilly
>
> Violations will cause a build to be marked as failed due to build
> configuration problems - for example if the coverage.py HTML path is empty or
> incorrect, the build will inaccurately be reported as failing and spam
> innocent committers. It should be marked as aborted or some other state
> indicating that the tests actually passed but there was something wrong
> within the Jenkins environment.
> {code}
> ERROR: failed to find coverage HTML reports
> Build step 'Publish coverage.py HTML reports' changed build result to FAILURE
> {code}
--
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
