-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Warnings Plugin v4.45
Static Analysis Collector Plugin v1.42
Static Code Analysis Plugin v1.67
In my job configuration I have two workspace file parsers set up for the Warnings Plugin - one to parse a jshint.xml file using the provided JSLint parser, and one to parse a pylint.log file with the provided PyLint parser.
Both of these correctly executed during the build, and in the build results each has an accurate count. But the aggregate "Static Analysis Warnings" section only includes the count of whichever warnings parser was defined first.
Reversing the order of the warnings parsers changes the aggregate count to be short by the other one.
(PyLint first, JSLint second):
PyLint Warnings - 4 warnings
JSLint Warnings - 118 warnings
Task Scanner - 33 open tasks
Static Analysis Warnings - 37 warnings
(JSLint first, PyLint second):
JSLint Warnings - 118 warnings
PyLint Warnings - 4 warnings
Task Scanner - 33 open tasks
Static Analysis Warnings - 151 warnings
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/analysis/collector/handler/WarningsHandler.java
http://jenkins-ci.org/commit/analysis-collector-plugin/ea1495360e1de42b570203e37809994c8d8632a8
Log:
[FIXED JENKINS-27086] Use aggregated warnings in analysis collector.
Also refactored the acceptance tests for analysis collector in order to get the warnings plugin integrated. Note that this requires analysis-core 1.71.