[
https://issues.jenkins-ci.org/browse/JENKINS-11718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159092#comment-159092
]
dogfood commented on JENKINS-11718:
-----------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_analysis-core
#10407|http://ci.jenkins-ci.org/job/plugins_analysis-core/10407/]
[FIXED JENKINS-11718] Don't evaluate new warnings when there is (Revision
3fd140495752b3a7e2e04f87d7d76aab37e8a7ea)
Result = SUCCESS
Ulli Hafner :
Files :
* src/main/java/hudson/plugins/analysis/core/BuildResultEvaluator.java
* src/main/java/hudson/plugins/analysis/core/BuildResult.java
* src/main/java/hudson/plugins/analysis/core/ParserResult.java
> Initial job build should ignore 'new warnings' threshold
> --------------------------------------------------------
>
> Key: JENKINS-11718
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11718
> Project: Jenkins
> Issue Type: Improvement
> Components: analysis-core
> Reporter: kutzi
> Assignee: Ulli Hafner
> Priority: Minor
>
> When I import a project with existing warnings - e.g. compiler errors and
> have the new compiler warnings threshold set to e.g. 1, my initial build will
> be unstable/failed and I never have the chance to get it stable.
> Would be nice if the 'new warnings' thresholds could be ignored for the 1st
> build.
--
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
