[
https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162573#comment-162573
]
SCM/JIRA link daemon commented on JENKINS-12424:
------------------------------------------------
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/warnings/WarningsResult.java
src/main/resources/hudson/plugins/warnings/Messages.properties
src/main/resources/hudson/plugins/warnings/Messages_de.properties
src/main/resources/hudson/plugins/warnings/Messages_fr.properties
src/main/resources/hudson/plugins/warnings/Messages_ja.properties
http://jenkins-ci.org/commit/warnings-plugin/a530b8e715536d3b5c3b040e0de569a303d0291f
Log:
[JENKINS-12424] Use messages from base class.
> More correct and specific build state change reasons from Warnings
> -------------------------------------------------------------------
>
> Key: JENKINS-12424
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12424
> Project: Jenkins
> Issue Type: Improvement
> Components: analysis-core, warnings
> Reporter: Greg Moncreaff
> Assignee: Ulli Hafner
> Priority: Minor
>
> I got this in my jobs console.
> [WARNINGS] Setting build status to FAILURE since total number of annotations
> exceeds the threshold 200: [HIGH, NORMAL, LOW]
> Two issues.
> 1. text says total, but this was actually a "compute status since reference
> build (new) gate.
> 2. text should say which specific criteria was exceeded
> 3. it doesn't tell you what the actual number/difference was
> E.g.
> [WARNINGS] Setting build status to FAILURE since number, 234, of new HIGH
> annotations exceeds the threshold of 200 by 34 or 17%.
--
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
