When you add a new method, two unit tests and the build breaks because you didn't use constants the way sonarqube wanted....

Welcome! Why does your build break because of sonarqube? Do you not regard its issues as guidelines instead of hard and fast rules?

@linux-colonel it breaks because someone here has set code coverage to be > 80%. And the rules have not yet been fine tuned, so everyone gets and email that the build has failed after my last commit. Which is why I'm still in the office trying to write more unit tests to fulfill the rules...

That's some tough standards you have to live up to! I'd recommend not having the build break because of all sonarqube rule violations. At the very most have it break for blocker and critical issues. They are only code smells after all. Happy testing!

"Jenkins build is back to normal " - yeey!