Findbugs vs. SonarQube Server

Findbugs is best suited even when you want to adapt to certain coding conventions and discover possible bugs beforehand and it's best suited for the java open source. whether you are a developer or a DevOps engineer you can even use it as a plugin in your Jenkins pipeline or any other build automation server and your developer tool such as visual studio as well.

Incentivized

Scenarios where SonarQube is well suited:

1. Large codebase: The tool's static analysis capabilities can help teams quickly identify and fix bugs, vulnerabilities, and code smells in large codebases.
2. Compliance and security: The tool can check the code against industry standards or regulations, such as OWASP and CWE, and identify any issues that need to be addressed.
3. Agile development: SonarQube can be integrated with CI/CD pipelines allowing teams to continuously monitor and improve code quality throughout the development process.
4. Teams using multiple languages: Teams that use multiple programming languages can benefit from using SonarQube, as the tool supports a wide range of languages and can be integrated with a variety of development tools.

Scenarios where SonarQube may be less appropriate:

1. Small codebase: Organizations with a small codebase may not see the full benefits of using SonarQube, as the tool's static analysis capabilities may be overkill for a smaller codebase.
2. Limited resources: Organizations with limited resources may find it difficult to set up and configure SonarQube, as the tool can be complex and may require specialized expertise.
3. Limited integration: Organizations that use development tools or IDEs that are not supported by SonarQube may find it difficult to integrate the tool into their existing development workflow.
4. Limited scalability: Large organizations with millions of lines of code may find SonarQube's performance and scalability to be an issue. It may take longer for the analysis to finish and the results may not be as accurate.

Incentivized

• Scan the code for existing bugs present
• It can detect an vulnerabilities and also show possible bad warnings
• Can help identify errors in advance to avoid code crash post deployment

Incentivized

• Generating code quality report
• Calculates junit coverage of the codebase very efficiently and precisely
• Highlights the bugs and vulnerabilities in our codebase
• Informs the user of the improvements which can be done to the code to make it cleaner
• SonarQube also suggests remediation and resolution of the problems it highlights

Incentivized

• It’s documentation is not always up to date
• Difficulty in finding a prper solution when an issue arises during its configuration
• has limited features

Incentivized

• It doesn't provide automatic pull request with fixes
• It doesn't provide insights about the libraries of the projects
• The administration management user interface could be simplified
• It doesn't provide an order to fix issues, like archives with more and frequent commits have top priority

Incentivized

It can improve in some user experience and usability parts, like the code view and the way we assign issues it's a bit hidden and not highlighted

Incentivized

We we easily able to integrate the SonarQube steps into our TFS process via the Microsoft Marektplace, we didn't have the need to call SonarQube support. We've used their online documentation and community forum if we ran into any issues.

Incentivized

Sonar cloud has its own cloud where all the code vulnerabilities are collected and stored as a whole whereas its a plugin that is used in a code itself but the cons is that SonarCloud needs a license if you want to use it privately and also requires personal access token authentication if used with an external service

Incentivized

SonarQube identifies significant more thing compared to the built-in suggestions in IntelliJ IDEA. The suggestions how to correct issues are also a lot better with SonarQube. IntelliJ IDEA provides great refactoring support to make it easy to refactor the code to solve issues. We use these tools together and they really complement each other.

Incentivized

• Its being used overall by most of the teams
• Some of the teams migrating to another testing tool as it has limited features
• Still recommend as its open source and beginners friendly

Incentivized

• Positive ROI from the standpoint of flagging several issues that would have otherwise likely been unaddressed and caused more time to be spent closer to launch
• Slightly positive ROI from time-saving perspective (it's an automated check which is nice, but depending on the issues it finds, can take developers time to investigate and resolve)