Several checkstyle reports should not aggregated in one violation report #77
Description
Hey,
in our web projects, we are using different technologies (e.g. PHP, JavaScript, SCSS). For each technology we are using a coding standard. The standards are controlled by different tools (e.g. PHP_CodeSniffer, JSCS, SCSSLinter), which generate checkstyle reports.
The aggregation of these checkstyle reports in the violations plugin is not readable and clearly represented, because different roles (frontend and backend developer) can not find the interesting results in one overview. They have to search for their results in an aggregated report, which mixes different reports.
I think, it make no sense to create a jenkins job for each report. It would be nice to extend the violations-plugin in the following way:
- The violations-plugin should not offer a fixed number of report types
- Instead it should be extensible: the user should decide how many reports he want to use
- For example: In the configuration menu, the user have a button to add a violation report. He can define a name for the report, which is also used in the graph. He can choose the report type from a dropdown (e.g. checkstyle, csslint, pmd, ...). He can define weather and status of the build and the XML filename pattern.
My english is not the best, so i hope, i was able to explain my vision in an understandable way. What do you think of my idea?
Unfortunately i'm not a java developer. So i can't adjust the plugin on my own.
Best regards,
Christian