[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162740#comment-162740 ] Ulli Hafner commented on JENKINS-12424: --- Integrated in !http://faktorzehn.org:8081/images/16x16/blue.png! [Jenkins Analysis Plug-ins (Compile) #502|http://faktorzehn.org:8081/job/Jenkins%20Analysis%20Plug-ins%20(Compile)/502/] [JENKINS-12424] Added links to new and priority warnings. (Revision b72cda9a98a5d11b5b4be355bf87d9aa30f55e86) Result = SUCCESS 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12424. --- Resolution: Fixed 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162748#comment-162748 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/BuildResultEvaluator.java src/main/resources/hudson/plugins/analysis/Messages.properties src/main/resources/hudson/plugins/analysis/Messages_de.properties http://jenkins-ci.org/commit/analysis-core-plugin/5c21e8054698196040a75cf4f18944b8bef94d51 Log: [Fixed JENKINS-12424] Added messages for one warning. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162759#comment-162759 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_analysis-core #10451|http://ci.jenkins-ci.org/job/plugins_analysis-core/10451/] [JENKINS-12424] Added links to new and priority warnings. (Revision b72cda9a98a5d11b5b4be355bf87d9aa30f55e86) [Fixed JENKINS-12424] Added messages for one warning. (Revision 5c21e8054698196040a75cf4f18944b8bef94d51) Result = SUCCESS Ulli Hafner : Files : * src/main/java/hudson/plugins/analysis/core/ReporterDescriptor.java * src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java * src/test/java/hudson/plugins/analysis/core/BuildResultEvaluatorTest.java * src/main/java/hudson/plugins/analysis/core/MavenResultAction.java * src/main/java/hudson/plugins/analysis/core/BuildResult.java * src/main/resources/hudson/plugins/analysis/Messages_de.properties * src/main/java/hudson/plugins/analysis/core/BuildResultEvaluator.java * src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java * src/main/resources/hudson/plugins/analysis/Messages.properties * src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java Ulli Hafner : Files : * src/main/resources/hudson/plugins/analysis/Messages_de.properties * src/main/java/hudson/plugins/analysis/core/BuildResultEvaluator.java * src/main/resources/hudson/plugins/analysis/Messages.properties 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162567#comment-162567 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/BuildResult.java src/main/java/hudson/plugins/analysis/util/HtmlPrinter.java src/main/resources/hudson/plugins/analysis/Messages.properties src/main/resources/hudson/plugins/analysis/Messages_de.properties src/main/resources/hudson/plugins/analysis/Messages_fr.properties src/main/resources/hudson/plugins/analysis/Messages_ja.properties src/test/java/hudson/plugins/analysis/core/BuildResultTest.java http://jenkins-ci.org/commit/analysis-core-plugin/882d0579575d069b2e45e4528dd70bb2ccc68020 Log: [JENKINS-12424] Pulled up build result summary message to BuildResult. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162568#comment-162568 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/dry/DryResult.java src/main/java/hudson/plugins/dry/ResultSummary.java src/main/resources/hudson/plugins/dry/Messages.properties src/main/resources/hudson/plugins/dry/Messages_de.properties src/main/resources/hudson/plugins/dry/Messages_ja.properties src/test/java/hudson/plugins/dry/ResultSummaryTest.java http://jenkins-ci.org/commit/dry-plugin/3b34bf609768117b4aa419de8b91bb7af8923ac9 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162572#comment-162572 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/analysis/collector/AnalysisResult.java src/main/java/hudson/plugins/analysis/collector/AnalysisResultSummary.java src/main/resources/hudson/plugins/analysis/collector/Messages.properties src/main/resources/hudson/plugins/analysis/collector/Messages_de.properties src/main/resources/hudson/plugins/analysis/collector/Messages_ja.properties src/test/java/hudson/plugins/analysis/collector/ResultSummaryTest.java http://jenkins-ci.org/commit/analysis-collector-plugin/5743c8c7b9035e3c4e0a1d0543f8307f6469029c 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162571#comment-162571 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/pmd/PmdResult.java src/main/java/hudson/plugins/pmd/ResultSummary.java src/main/resources/hudson/plugins/pmd/Messages.properties src/main/resources/hudson/plugins/pmd/Messages_de.properties src/main/resources/hudson/plugins/pmd/Messages_fr.properties src/main/resources/hudson/plugins/pmd/Messages_ja.properties src/test/java/hudson/plugins/pmd/ResultSummaryTest.java http://jenkins-ci.org/commit/pmd-plugin/933785d4f694c9bbbd07f18b17e8badf0dff4953 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162570#comment-162570 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: plugin/pom.xml plugin/src/main/java/hudson/plugins/findbugs/FindBugsResult.java plugin/src/main/java/hudson/plugins/findbugs/ResultSummary.java plugin/src/main/resources/hudson/plugins/findbugs/Messages.properties plugin/src/main/resources/hudson/plugins/findbugs/Messages_de.properties plugin/src/main/resources/hudson/plugins/findbugs/Messages_ja.properties plugin/src/test/java/hudson/plugins/findbugs/ResultSummaryTest.java http://jenkins-ci.org/commit/findbugs-plugin/fbbb1fef2619c783f0ee49a652234cb127b737f4 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162569#comment-162569 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/checkstyle/CheckStyleResult.java src/main/java/hudson/plugins/checkstyle/ResultSummary.java src/main/resources/hudson/plugins/checkstyle/Messages.properties src/main/resources/hudson/plugins/checkstyle/Messages_de.properties src/main/resources/hudson/plugins/checkstyle/Messages_fr.properties src/main/resources/hudson/plugins/checkstyle/Messages_ja.properties src/test/java/hudson/plugins/checkstyle/ResultSummaryTest.java http://jenkins-ci.org/commit/checkstyle-plugin/c9863ac5e7a939f58897200225a724063555f08f 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162576#comment-162576 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/checkstyle/CheckStyleResultAction.java http://jenkins-ci.org/commit/checkstyle-plugin/f0fab6a73c1197d5f78b2493789c3e4ae9692f5b Log: [JENKINS-12424] Pulled up tool tips. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162575#comment-162575 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java http://jenkins-ci.org/commit/analysis-core-plugin/fde91c34942a51e50d8be0d2eba7df08ed52534b Log: [JENKINS-12424] Pulled up tool tips. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162577#comment-162577 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/dry/DryResultAction.java http://jenkins-ci.org/commit/dry-plugin/e0c7b51ab19fe8749a0be2b8d105d0c2f820d210 Log: [JENKINS-12424] Pulled up tool tips. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162579#comment-162579 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: plugin/src/main/java/hudson/plugins/findbugs/FindBugsResultAction.java http://jenkins-ci.org/commit/findbugs-plugin/09423284d787f23cd1397070c43303967a3451ce Log: [JENKINS-12424] Pulled up tool tips. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162581#comment-162581 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/collector/AnalysisResultAction.java http://jenkins-ci.org/commit/analysis-collector-plugin/6d57f9725542884510355622b84692b0ede612ea Log: [JENKINS-12424] Pulled up tool tips. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162582#comment-162582 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_analysis-core #10448|http://ci.jenkins-ci.org/job/plugins_analysis-core/10448/] [JENKINS-12424] Pulled up build result summary message to BuildResult. (Revision 882d0579575d069b2e45e4528dd70bb2ccc68020) Result = SUCCESS Ulli Hafner : Files : * src/main/resources/hudson/plugins/analysis/Messages_fr.properties * src/main/resources/hudson/plugins/analysis/Messages_de.properties * src/test/java/hudson/plugins/analysis/core/BuildResultTest.java * src/main/resources/hudson/plugins/analysis/Messages_ja.properties * src/main/resources/hudson/plugins/analysis/Messages.properties * src/main/java/hudson/plugins/analysis/util/HtmlPrinter.java * src/main/java/hudson/plugins/analysis/core/BuildResult.java 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162580#comment-162580 ] SCM/JIRA link daemon commented on JENKINS-12424: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsResultAction.java http://jenkins-ci.org/commit/warnings-plugin/27ced4879f77753a48b4ab60a7a0e09426758ef8 Log: [JENKINS-12424] Pulled up tool tips. 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162583#comment-162583 ] Ulli Hafner commented on JENKINS-12424: --- Integrated in !http://faktorzehn.org:8081/images/16x16/blue.png! [Jenkins Analysis Plug-ins (Compile) #495|http://faktorzehn.org:8081/job/Jenkins%20Analysis%20Plug-ins%20(Compile)/495/] [JENKINS-12424] Pulled up tool tips. (Revision fde91c34942a51e50d8be0d2eba7df08ed52534b) Result = SUCCESS 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162584#comment-162584 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_analysis-core #10449|http://ci.jenkins-ci.org/job/plugins_analysis-core/10449/] [JENKINS-12424] Pulled up tool tips. (Revision fde91c34942a51e50d8be0d2eba7df08ed52534b) Result = SUCCESS Ulli Hafner : Files : * src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162586#comment-162586 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_checkstyle #346|http://ci.jenkins-ci.org/job/plugins_checkstyle/346/] Result = SUCCESS 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162587#comment-162587 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_dry #349|http://ci.jenkins-ci.org/job/plugins_dry/349/] Result = SUCCESS 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162585#comment-162585 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_analysis-collector #354|http://ci.jenkins-ci.org/job/plugins_analysis-collector/354/] Result = SUCCESS 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162590#comment-162590 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png! [plugins_warnings #408|http://ci.jenkins-ci.org/job/plugins_warnings/408/] Result = UNSTABLE 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162589#comment-162589 ] dogfood commented on JENKINS-12424: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_pmd #348|http://ci.jenkins-ci.org/job/plugins_pmd/348/] Result = SUCCESS 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner reopened JENKINS-12424: --- Yes, that would improve that usability even more. Since this feature needs the HTML links from the individual plug-ins, changes to all plug-ins are required (and not only to analysis-core). So this will take some time... 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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[
https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158745#comment-158745
]
Ulli Hafner edited comment on JENKINS-12424 at 2/7/12 9:19 PM:
---
Ok, I added the message to the build summary:
{code}
BuildResultEvaluator.failure.new.priority={0} new warnings of priority {3}
exceeded the threshold of {1} by {2}
BuildResultEvaluator.failure.all.priority={0} warnings of priority {3} exceed
the threshold of {1} by {2}
BuildResultEvaluator.failure.new={0} new warnings exceeded the threshold of {1}
by {2}
BuildResultEvaluator.failure.all={0} warnings exceed the threshold of {1} by {2}
{code}
Can you please check if these messages are ok (and correct English)? The
numbers in the brackets are replaced by values.
was (Author: drulli):
Ok, I added the message to the build summary:
{code}
BuildResultEvaluator.failure.new.priority={0} new warnings of priority {3}
exceeded the threshold of {1} by {2}
BuildResultEvaluator.failure.all.priority={0} warnings of priority {3} exceed
the threshold of {1} by {2}
BuildResultEvaluator.failure.new={0} new warnings exceeded the threshold of {1}
by {2}
BuildResultEvaluator.failure.all={0} warnings exceed the threshold of {1} by {2}
{code}
Can you please check if these messages are ok (and correct english)? The
numbers in the brackets are replaced by values.
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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[
https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158745#comment-158745
]
Ulli Hafner edited comment on JENKINS-12424 at 2/7/12 9:21 PM:
---
Ok, I added the message to the build summary:
{code}
BuildResultEvaluator.failure.new.priority={0} new warnings of priority {3}
exceed the threshold of {1} by {2}
BuildResultEvaluator.failure.all.priority={0} warnings of priority {3} exceed
the threshold of {1} by {2}
BuildResultEvaluator.failure.new={0} new warnings exceed the threshold of {1}
by {2}
BuildResultEvaluator.failure.all={0} warnings exceed the threshold of {1} by {2}
{code}
Can you please check if these messages are ok (and correct English)? The
numbers in the brackets are replaced by values.
was (Author: drulli):
Ok, I added the message to the build summary:
{code}
BuildResultEvaluator.failure.new.priority={0} new warnings of priority {3}
exceeded the threshold of {1} by {2}
BuildResultEvaluator.failure.all.priority={0} warnings of priority {3} exceed
the threshold of {1} by {2}
BuildResultEvaluator.failure.new={0} new warnings exceeded the threshold of {1}
by {2}
BuildResultEvaluator.failure.all={0} warnings exceed the threshold of {1} by {2}
{code}
Can you please check if these messages are ok (and correct English)? The
numbers in the brackets are replaced by values.
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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[
https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158745#comment-158745
]
Ulli Hafner commented on JENKINS-12424:
---
Ok, I added the message to the build summary:
{code}
BuildResultEvaluator.failure.new.priority={0} new warnings of priority {3}
exceeded the threshold of {1} by {2}
BuildResultEvaluator.failure.all.priority={0} warnings of priority {3} exceed
the threshold of {1} by {2}
BuildResultEvaluator.failure.new={0} new warnings exceeded the threshold of {1}
by {2}
BuildResultEvaluator.failure.all={0} warnings exceed the threshold of {1} by {2}
{code}
Can you please check if these messages are ok (and correct english)? The
numbers in the brackets are replaced by values.
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
[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158746#comment-158746 ] Greg Moncreaff commented on JENKINS-12424: -- Messages look fine. Thank you for doing this! 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
