“分析收集器"或"SONAR"詹金斯? [英] "Analysis collector" or "SONAR" for Jenkins?
问题描述
我正在考虑将静态代码分析添加到我们的Java项目的Jenkins构建中(约50万行代码).
SONAR的优点之一是它可以显示解决方案
Sonar不仅是在统一环境中集成其他工具的工具.首先，借助Sonar，您不仅可以分析Java源代码，还可以分析使用20多种语言开发的代码. http://www.sonarsource.com/products/plugins/languages/
然后，Sonar的主要功能是差异视图，您可以在其中查看代码质量随时间的变化情况.老实说，这不能通过单独使用这些工具来完成. http://docs.codehaus.org/display/SONAR/Differential+Views
此外，您可以创建代码审查并将其与Jira集成(如果使用)，并可以从40多个开源和商业插件中受益，这些插件可以在Sonar安装中添加更多功能.
因此恕我直言，您提到的两个工具甚至无法比较！ 我肯定会建议Sonar
I'm looking at adding static code analysis to our Jenkins builds of a Java project (~500K lines of code).
Two possibilities are Analysis Collector or SONAR.
One advantage of SONAR looks to be it can show dead code and deprecated methods.
Recommendations?
Sonar is not just a tool to integrate other tools in a unified environment. First with Sonar you can analyze not just Java source code but code developed in more than 20 languages. http://www.sonarsource.com/products/plugins/languages/
Then the star feature of Sonar is the differential views where you can see how the quality of your code is evolving over time. To be honest this can't be done by using these tools in separately. http://docs.codehaus.org/display/SONAR/Differential+Views
Furthermore you can create code reviews and integrate it with Jira (if you use it) and benefit from over 40 open source and commercial plugins that add more features into your Sonar installation.
So IMHO the two tools you mention can't be even compared! And I'd definitely suggest Sonar
这篇关于“分析收集器"或"SONAR"詹金斯?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
