-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: fail checkstyle on all findings except warning.LOW #4899
Conversation
Meh, that somehow does not work as expected 🤔 |
* we did not put enough effort into fixing pmd and spotbugs issues to apply these strict quality gates for them
I think I fixed the syntax errors @jdrueckert |
* <li><a href="https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/application-verifier">Application Verifier | ||
* (<code>AppVerif.exe</code>)</a>, available from the Windows SDK</li> | ||
* <li> | ||
* <a href="https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/application-verifier">Application Verifier (<code>AppVerif.exe</code>)</a>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any clue about getting rid of this LineLenghtCheck. sometimes its better to format this with one long line.
I think this is a lot more readable then trying to work out how to chop the line to the right length.
* <ul>
* <li><a href="https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/application-verifier">Application Verifier (<code>AppVerif.exe</code>)</a>,available from the Windows SDK</li>
* <li><a href="https://github.com/lowleveldesign/process-governor">Process Governor (<code>procgov</code>)</a>,an open source third-party tool</li>
* </ul>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @skaldarnar mentioned on Discord, for these "sometimes" cases there's annotations that allow exactly that: ignoring the check rule in a particular case.
maybe we can adjust the checkstyle warnings: https://checkstyle.sourceforge.io/property_types.html#SeverityLevel |
Currently, the analysis stage only fails for findings of severity "error".
Findings of severities "warning.HIGH", "warning.NORMAL" and "warning.LOW" do not result in a failure.
This PR attempts to reduce the acceptable severity to "warning.LOW" only, all findings of higher severities should fail the build.