[GRADLE-2993] Add an option to pass "-quiet" to Findbugs plugin Created: 20/Jan/14 Updated: 02/Feb/17 Resolved: 02/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | ||
| Reporter: | Gradle Forums | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 4 |
| Description |
|
Currently the Findbugs logs a lot of messages regarding Analyzing..., Scanning archives..., analysis passes, etc. These can be suppressed by adding -quiet to the command line or adding the following line to FindBugsExecuter: commandLine.parse(new String[] {"-quiet"}); The biggest issue is that some of these messages get picket as targets by Jenkins, which totally ruins the layout of the build report page. I tried to override the FindBugsExecuter from the buildSrc, but it was not picked up. |
| Comments |
| Comment by Chuck May [ 18/Apr/16 ] |
|
We are still struggling with this issue. If you have a --parallel build which runs Findbugs, then the log gets completely flooded with Findbugs messages. [08:58:35] : [Step 1/1] Scanning archives (0 / 220) This was detailed in this thread. https://discuss.gradle.org/t/add-an-option-to-pass-quiet-to-findbugs-plugin/554 If you do not run in parallel, then those messages are not logged. Here is the last comment of the thread:
|
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Chuck May [ 15/Nov/16 ] |
|
I really hope this bug gets migrated to Github and looked at. This has been an issue for literally years and makes the logs very difficult to process. |
| Comment by Benjamin Muschko [ 02/Feb/17 ] |
|
The work is now tracked here: https://github.com/gradle/gradle/issues/1307 |