Welcome
this might be possible in an open environment, but not for Enterprise customers - think of banks or insurance companies with strict safety requirements .
It is bad enough that “sonar.exclusions” can be used as a scanner property
which versions are you using - SonarQube 8.9.2 LTS
what are you trying to achieve - Avoid or report the use of sonar.exclusions
what have you tried so far to achieve this - Found nothing relevant or working
Hello everybody,
I would like to block our developpers to use sonar.exclusions to avoid the sonar analysis.
I doubt that there is a way to block it but I would like to know if there is a way to emit a report (mail) when an analysis using it is possible.
Thanks for your help,
Michel
and this should still be considered
Hi Randy,
it’s also possible to suppress more than one rule via @SuppressWarnings({“squid:xxx”,“squid:xxx”})
See documentation
As Sonarqube admin be sure to use:
squid:S1309 ‘Track uses of “@SuppressWarnings” annotations’
with an appropriate whitelist to prevent some clever developers
using @SuppressWarnings("all") in all their classes
squid:NoSonar ‘Track uses of “NOSONAR” comments’
to prevent the use of //NOSONAR for hiding issues
Also note that issues for rules working on file…
Gilbert
