We like the data that Sonatype Nexus Lifecycle consistently delivers. This solution helps us in fixing and understanding the issues a lot quicker. The policy engine allows you to set up different types of violations according to your specific needs. It allows us to see the licensing and security vulnerabilities as well as the age of our open sources in our software. This helps us ensure we stay up to date with our software and that we don’t have any vulnerabilities.
We would really like to see Sonatype Nexus Lifecycle be more code-driven and scaled at the developer level. It really should be smoother and faster at finding the relationships between libraries and enterprises. The GUI has some limitations and could be problematic for some larger-scale companies.
SonarQube is easy to deploy and configure. It also integrates well with other tools to do quality code analysis. SonarQube has a great community edition, which is open-source and free. It is great if you want to quickly focus on functional requirements. This solution is very easy to use and understand.
There were some security issues with our code that SonarQube did not find. Defining the quality of rules should be improved to ensure that low-performance code does not move forward to production. We would like to see better security scanning and statistical analysis from this solution.
Conclusion
Both of these are amazing, highly-regarded solutions. We chose Sonatype Nexus as a better fit for us. We felt that SonarQube needed multiple other products in order to function well and was lacking in some of the reporting qualities we desired. We felt that the proprietary data that Sonatype Nexus provides with regard to libraries was a great characteristic for us. We found that this solution integrates well with the other products we are using. We especially like the REST API, which we can drive remotely and automate.
SonarQube Server and Sonatype Lifecycle compete in software quality and security management solutions. Sonatype Lifecycle may have the upper hand in security features, whereas SonarQube offers strength in customization and language support.Features: SonarQube Server is known for customizable quality profiles, gates, and integration with CVS. It supports over 20 programming languages and provides unit tests, code coverage, quality gate controls, and has a vibrant community. Sonatype Lifecycle...
We like the data that Sonatype Nexus Lifecycle consistently delivers. This solution helps us in fixing and understanding the issues a lot quicker. The policy engine allows you to set up different types of violations according to your specific needs. It allows us to see the licensing and security vulnerabilities as well as the age of our open sources in our software. This helps us ensure we stay up to date with our software and that we don’t have any vulnerabilities.
We would really like to see Sonatype Nexus Lifecycle be more code-driven and scaled at the developer level. It really should be smoother and faster at finding the relationships between libraries and enterprises. The GUI has some limitations and could be problematic for some larger-scale companies.
SonarQube is easy to deploy and configure. It also integrates well with other tools to do quality code analysis. SonarQube has a great community edition, which is open-source and free. It is great if you want to quickly focus on functional requirements. This solution is very easy to use and understand.
There were some security issues with our code that SonarQube did not find. Defining the quality of rules should be improved to ensure that low-performance code does not move forward to production. We would like to see better security scanning and statistical analysis from this solution.
Conclusion
Both of these are amazing, highly-regarded solutions. We chose Sonatype Nexus as a better fit for us. We felt that SonarQube needed multiple other products in order to function well and was lacking in some of the reporting qualities we desired. We felt that the proprietary data that Sonatype Nexus provides with regard to libraries was a great characteristic for us. We found that this solution integrates well with the other products we are using. We especially like the REST API, which we can drive remotely and automate.