Error in jenkins during sonar analysis caused by svn blame

耗尽温柔 提交于 2019-12-03 11:01:57

In SonarQube v4, go to your project's dashboard and then to Project Configuration \ Settings (top right under the Search box).

Click the SCM Activity link in the Category list and change the "Activation of..." drop down to false.

You can change the default on the global settings page.

Just add the property sonar.scm.disabled=true into sonar-runner/conf/sonar-runner.properties. I have just tested it with SonarQube 5.1.1.

In the last release of Sonar (SonarQube v 5.0.1), property is set to true in order to deactivate the SCM Sensor. So choose "True" to disable SCM and solve this issue :)

In Sonarqube server version Version 5.6.1 Click on Administration -> click on Configuration Dropdown and select General settings -> Click on SCM -> Select the true in Disable the SCM Sensor drop-down and save SCM settings(The default selected means is false).

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!