如何在 sonarqube 5.0 中使用 git 作为 scm 提供程序(使用 sonar-runner) [英] How can I use git as the scm provider in sonarqube 5.0 ( using sonar-runner )
问题描述
我关注 sonarqub 的官方支持http://docs.sonarqube.org/display/SONAR/SCM+support
I following the official support of sonarqub http://docs.sonarqube.org/display/SONAR/SCM+support
我得到了上面的错误.
我是否错过了需要配置的东西,或者配置错误
did I miss something need to config, or configure wrong
08:46:33.723 INFO - Sensor SCM Sensor...
08:46:33.897 INFO - SCM provider for this project is: git
08:46:33.898 INFO - Retrieve SCM blame information...
08:46:33.915 INFO - 632 files to be analyzed
08:46:34.377 INFO - Author: PersonIdent[Not Committed Yet, , Tue Feb 3 08:46:34 2015 +0000]
08:46:34.379 INFO - Source commit: null
08:46:34.377 INFO - Author: PersonIdent[Not Committed Yet, , Tue Feb 3 08:46:34 2015 +0000]
08:46:34.924 INFO - Source commit: null
INFO: ------------------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: ------------------------------------------------------------------------
Total time: 1:01.699s
08:46:35.891 INFO - Author: PersonIdent[Not Committed Yet, , Tue Feb 3 08:46:35 2015 +0000]
08:46:34.930 INFO - Author: PersonIdent[Not Committed Yet, , Tue Feb 3 08:46:34 2015 +0000]
08:46:35.930 INFO - Source commit: null
Final Memory: 27M/318M
INFO: ------------------------------------------------------------------------
ERROR: Error during Sonar runner execution
ERROR: Unable to execute Sonar
ERROR: Caused by: Unable to blame file
非常感谢.
推荐答案
这是因为在运行分析时,SonarQube 期望所有文件都应该提交.
This is because when running an analysis, SonarQube expects that all files should be committed.
确实,SonarQube 假定当您运行标准分析(将数据推送到服务器)时,项目的单个文件不应有任何未提交的更改,因为这可能会推送不相关的信息与存储库中的真实源代码.这就是分析失败的原因.
Indeed, SonarQube assumes that when you run a standard analysis (that pushes data to the server), there should not be any uncommitted changes on a single file of the project, because this would potentially push information that won't be relevant with the real source code on the repository. That's why the analysis will fail.
运行预览分析时显然不是这种情况:由于这种分析不会将数据推送到服务器,仅在本地报告问题,因此未提交的更改不是问题,因此分析不会失败.
This is obviously not the case when you run a preview analysis: as this kind of analysis does not push data to the server and only reports issues locally, then it's not a problem to have uncommitted changes and the analysis will therefore not fail.
我已经更新了文档,以使这一点更加清晰.
I've updated the documentation to make this clearer.
这篇关于如何在 sonarqube 5.0 中使用 git 作为 scm 提供程序(使用 sonar-runner)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!