![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Ulli Hafner
|
|
Components:
|
analysis-collector-plugin, warnings-plugin |
|
Created:
|
23/Feb/15 3:57 PM
|
|
Description:
|
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
|
|
Environment:
|
Warnings Plugin v4.45
Static Analysis Collector Plugin v1.42
Static Code Analysis Plugin v1.67
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Evan Gilbert
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
