|title||On by default|
All SCM providers currently require the native executable to be installed on the server where the SonarQube analysis will run. For example, for projects hosted on a Subversion repository and analysed on a Jenkins server, an svn executable must be available on the Jenkins server (and its slaves if any).
Subversion (1.6+ client)
- tested by users
Information are automatically retrieved from the .git, .svn, etc. folders. Therefore, nothing has to be configured and no configuration will be taken into account.
Configuring the SCM Activity Plugin: SCM other than SVN, Git and Mercurial
Forcing the Retrieval of Blame Information
In some cases, it is necessary to retrieve blame information on files that have not been changed (for example when a user has been renamed). To force this retrieval, here are the steps to follow:Deactivate the SCM Activity plugin at the project level:
sonar.scm.enabled = false
sonar.scm.enabled = true
Note that a property should be added sooner or later to explicitly force this retrieval or not. See SONARPLUGINS-2359.
The simplest workaround is to always set autocrlf to "false" on the box doing the SonarQube analysis.
Specific configuration for Jazz RTC
Additional configuration for Perforce