Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
{iframe:src=http://update.sonarsource.org/plugins/scmactivity-confluence.html|width=700|height=250350|frameborder=0}
Your browser does not support iframes.
{iframe}
Warning
titleDeprecated

This plugin is deprecated since SonarQube 5.0 which has built-in support for SCM information and which relies on independent plugins to cover SCM providers.

Description / Features

This plugin collects SCM blame information and displays the date of the commit and the commiter ID to the left of each line of code:

Image RemovedImage Added

This plugin also enables the computation of:

...

This plugin is enabled by default for all projects. The SCM Activity plugin can be disabled on a project-by-project basis, or disabled globally at Settings > General Settings > SCM Activity and then enabled on a project-by-project basis.

For more detail on how to see SCM data in the code, please see the SCM Information tab section of the Component Viewer documentation.

Requirements

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).

Plugin

1.3

1.41.51.61.7.11.8

Subversion (1.6+ client)

(tick)

(tick)(tick)(tick)(tick)(tick)

Git

(tick)

(tick)(tick)(tick)(tick)(tick)

Mercurial

(tick)

(tick)(tick)(tick)(tick)(tick)

CVS

(tick)

(tick)(tick)(star)(star)(star)

Perforce

(question)

(question)(star)(star)(star)(star)

ClearCase

(error)

(question)(star)(star)(star)(star)

Bazaar

(question)

(question)(question)(question)(question)(question)

Team Foundation Server (all versions)

Requires SonarTfsAnnotate.exe to be
installed and available from the %PATH%. 

(error)

 

(error)

(error)

(error)

(error)

(tick)

Accurev

(question)

(question)(question)(question)(question)(question)
Jazz RTC(error)(question)(question)(star)(star)(star)
MKS Integrity(error)(question)(question)(question)(question)(question)
Visual SourceSafe

(error)

(error)(error)(error)(error)(error)
CM Synergy

(error)

(error)(error)(error)(error)(error)

StarTeam

(error)

(error)(error)(error)(error)(error)

(tick) - supported

(star) - tested by users

...

Include Page
Include - Plugin Installation
Include - Plugin Installation

Usage

Configuring the SCM Activity Plugin: SVN, Git

...

, Mercurial and Team Foundation Server (TFS)

Information are is automatically retrieved from the .git, .svn, $tf, etc. folders. Therefore, nothing has to be configured and no configuration will be taken into account.

In order for this to work, the sonar-project.properties file needs to be located in a checked-out folder, but it does not have to be checked-in.
Alternatively, you can set the "sonar.projectBaseDir" property to a checked-in folder (requires sonar-runner 2.4 at least), and have the sonar-project.properties files located anywhere.

Configuring the SCM Activity Plugin:

...

Others

At the project level, go to Configuration > Settings > SCM Activity

...

Forcing the Retrieval of Blame Information

 

Info

Note that a property should be added sooner or later to explicitly force this retrieval or not. See SONARPLUGINS-2359.

 

Troubleshooting

Subversion "Server certificate verification failed: issuer is not trusted"

...

Since version 1.6, you have to set an additional property to define the Perforce client name while running your analysis: sonar.scm.perforce.clientspec.name.Prior to version 1.6, you have to set an additional property to define the Perforce client name while running your analysis: maven.scm.perforce.clientspec.name. This property can only be passed via command line (do not set it in the sonar-project.properties file).

Example:

Code Block
languagenone
sonar-runner -Dmaven.scm.perforce.clientspec.name=myPerforceClientName