<< Back to previous view |
[QB-2016] Codenarc Report Support
|
|
Status: | Resolved |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | 6.1.0 |
Type: | New Feature | Priority: | Major |
Reporter: | Brandon Zeeb | Assigned To: | Steve Luo |
Resolution: | Fixed | Votes: | 6 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown |
Description |
Please support Codenarc XML results. Example can be shown here:
http://codenarc.sourceforge.net/SampleCodeNarcXmlReport.xml My company (OCLC) has many Groovy projects built with Gradle with Codenarc enabled. It would be of great value to us to have native Codenarc reports supported. Thanks in advance. |
Comments |
Comment by Maikel vd Hurk [ 20/Apr/14 10:03 AM ] |
Dont see this support in 5.1.22, loods like one commit was having wrong description pointing to this feature request |
Comment by Don Ross [ 10/Mar/15 05:36 PM ] |
I have been able to publish a CodeNarc html report using the built-in HTML report functionality in QuickBuild.
What are the additional benefits you get from having an XML report? (Please help me understand what I am missing). |
Comment by Jonathan Baker [ 17/Aug/15 08:05 PM ] |
The benefit is the same as for any of the reports that QB currently publishes because it aggregates the results from multiple project modules into one report. Codenarc works just like junit or clover in that if you have a project that looks like this:
root ->sub-module-a ->sub-module-b A codenarc report is created at both the sub-module-a and sub-module-b level. QB could be the aggregator of all the sub-reports into one big report. (which appears to be exactly what it does for clover, junit, etc) |