-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.89.2 on Windows
Warnings Plug-in 4.64
When the Warnings Plug-in parses a JCReport file, it expects the severity levels to be capitalized, like "Error" or "Warning": https://github.com/jenkinsci/warnings-plugin/blob/warnings-4.64/src/main/java/hudson/plugins/warnings/parser/jcreport/JcReportParser.java#L83
However, JCReport itself appears to use lower-case severity levels "error" and "warning": https://github.com/jCoderZ/fawkez-code-report/blob/5624ac77dcd11067f27b001bcb1ee3f1c06076e2/fawkez-code-report-core-base/src/main/java/org/jcoderz/phoenix/report/Severity.java and https://github.com/jCoderZ/fawkez-code-report/blob/5624ac77dcd11067f27b001bcb1ee3f1c06076e2/fawkez-code-report-core/src/main/resources/xjc/report-types.xsd
I have not tested the behavior of JCReport in practice.
Split from JENKINS-48669.
- is related to
-
-
- Resolved
-
[JENKINS-48720] Warnings Plugin wants "Error" but JCReport apparently writes "error"
Kalle Niemitalo
created issue -
Kalle Niemitalo
made changes -
| Link |
New:
This issue is related to |
| Component/s | New: analysis-model [ 23523 ] | |
| Component/s | Original: warnings-plugin [ 15513 ] | |
| Assignee | Original: Ulli Hafner [ drulli ] | |
| Labels | Original: parser | New: help-wanted newbie-friendly |
| Priority | Original: Minor [ 4 ] | New: Trivial [ 5 ] |
| Epic Link |
New:
|
| Priority | Original: Trivial [ 5 ] | New: Minor [ 4 ] |
Tobias Redl
made changes -
| Assignee | New: Tobias Redl [ redto ] |
Tobias Redl
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Tobias Redl
made changes -
| Rank | New: Ranked higher |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
