Can I get an opinion on SonarQube? In particular enforcing sonar quality gates in build jobs (for teams other than mine). I argued that it is useful at work and was blatantly told it has never ever prevented bugs. While I'm VERY familiar with it's functionality I am unsure how to argue for it to be in use. Obviously I'm in favor of it, and my experience is if the quality gates are unenforced the results are largely ignored. Yes I'm aware that devs want less barriers to their job, but automated testing (in all it's various forms) is mostly a productive thing. (...or maybe there is no business case for SonarQube to exist as a company, that's possible too.)

Hi 👋 I am actually on the other side of it, however, I think sonarqube pushes me to write better code. I mean yes it can't catch all logical problems ( neither do I 😄 ) but forcing a quality level helps me to maintain a readable code base, some of my commits only aims to resolve code smells reported by sonarqube, it is kinda relaxing 😄

How do I present a business argument for that?

well, first of all sonarqube makes you to write your unit tests, in my opinion this is so valuable for new/immature projects cause its overlooked most of the time(urgent new features 😄 ), all the other measurements (code smells, cognitive complexity, duplication) are simply an indicator for readability of the project. Your developer team might be doing excellent work, and you can unburden them with unimportant stuff for the team since all the thresholds are adjustable, however, it gets more and more challenging to keep the standards high when new people are involved in.