SonarQube has been really helpful for our development team in keeping the overall quality of our code high. What I like most is that it provides a clear view of code quality through metrics like code coverage, bugs, vulnerabilities, code smells, and code duplication. We have configured quality gates for our projects, which makes it easier to ensure that new code meets our expected quality standards. It also helps us catch issues early during development instead of finding them later in production. Overall, it gives us better visibility into our codebase and helps us maintain cleaner and more reliable code. Review collected by and hosted on G2.com.

Sometimes SonarQube can be a little noisy, as it flags certain issues that are not always relevant to our project. We have to manually review some findings and adjust the rules based on our requirements. Another thing is that the initial configuration, especially integrating code coverage reports and setting up quality gates, takes some time. Analysis can also add a little extra time to the CI/CD pipeline. It would be nice if the tool could provide more flexibility and simpler configuration options. Review collected by and hosted on G2.com.