fo2rist
04/13/2020, 6:09 PMprocessors:
active: true
exclude:
- 'DetektProgressListener'
- 'FunctionCountProcessor'
- 'PropertyCountProcessor'
- 'ClassCountProcessor'
- 'PackageCountProcessor'
- 'KtFileCountProcessor'
console-reports:
active: true
exclude:
- 'ProjectStatisticsReport'
- 'ComplexityReport'
- 'FindingsReport'
- 'NotificationReport'
- 'BuildFailureReport'
Example of output:Artur Bosch
04/13/2020, 7:41 PMFileBasedFindingsReport
.
I don't quite know what you mean with "only the summary (number of issues found)". Maybe you just want the BuildFailureReport
and inspect the html or xml reports ?fo2rist
04/13/2020, 7:49 PMThere is an additional console report which you may want to considerThanks, will check.
I don't quite know what you mean with "only the summaryWith previous version of Detekt I used to see something like
Build succeeded with 28 weighted issues (threshold defined was 48).
on success, but now it's gone I only see Build failed with 48 weighted issues (threshold defined was 48)
on failures. Is it possible to get this message back for success?Artur Bosch
04/14/2020, 12:19 PMConsoleReport
.
We have removed this message together with the BuildFailureReport
.
Another way would be to implement a custom Gradle tasks and count the detekt issues in the xml report.fo2rist
04/14/2020, 5:17 PM