A common problem we have at work is people committing code without having noticed that they're increasing the number of compiler warnings.
The ultimate goal is to make warnings errors, but until the count gets to zero, there's no clean way to do it.
We use Bitbucket for the pull request process, so it seems like that would be a fairly sensible place to display the warnings.
We use Jenkins for the build, and it already has a plugin which shows the compiler warnings in a report, but it isn't very visible when doing the PR.
I am also sitting on a Gradle plugin which can generate compiler warning reports without having to go to the build server, in case that will be of any use here.
Is there an integration where we can get the compiler warnings to show up on the Bitbucket PR?
(Note that SonarQube is not a valid answer to this question, as what it detects is a different subset of problems to what the compiler itself detects.)
0 Answers