|
Currently using SonarQube at the company where i work - since the scanning is async, the CI builds typically don't wait for it to be finished, otherwise the lead time for changes would grow (e.g. not one of those places where a server farm would run integration tests overnight either) and additional configuration would be necessary, for which there are no resources at the time. Furthermore, SonarQube doesn't let you automatically enable e-mail notifications for everyone: https://docs.sonarqube.org/latest/instance-administration/no... > Only users who subscribe themselves will get notifications. With only one exception, there is no admin functionality to proactively subscribe another user. If you believe a user should be receiving notifications, then it's time to practice the gentle art of persuasion. So everyone is also free to ignore the e-mails that they may or may not receive. This isn't made any easier by the default quality profiles being problematic to deal with, e.g. SonarQube asking you to add HTML tags which would break XHTML templating in certain frameworks, such as PrimeFaces, thus having to spend a lot of time marking stuff as false positives, since that actual check might be sometimes useful except for your particular circumstances, of which it is not aware. So perhaps it's a good idea to indeed utilize a language or another integrated solution (versioned/shared IDE code style preferences are also pretty cool), since other solutions, although workable with a bit of effort, wouldn't necessarily thrive in all environments. Unless, of course, you want to find a different environment, but that's a slightly different discussion. |