{iframe:src=http://update.sonarsource.org/plugins/scmactivity.html|width=700|height=250|frameborder=0}
Your browser does not support iframes.
{iframe}

...

Compatibility Matrix

All SCM providers currently require the native executable to be installed on the boxserver where the Sonar analysis will run. For example svn.exe must be available in PATH for Subversion projects, for projects hosted on a Subversion repository and analysed on a Jenkins server, svn executable must be available on the Jenkins server (and its slaves if any).

12+ 12 SONARPLUGINS-1291 SONARPLUGINS-1094 Accurev

Plugin	0.1 0.2	1.0	1.1	1.2	1.3	1.4	Sonar	1.	5
Subversion (1.	6+	2.0+	2.0+	2.7+	2.7+	2.7+	Subversion		client)
1.6+ client		Git
		CVS
Mercurial
Bazaar		SONARPLUGINS-1157	Bazaar
Perforce
Perforce Team Foundation Server
ClearCase	StarTeam
Accurev				Team Foundation Server
Jazz RTC
MKS Integrity			ClearCase
Visual SourceSafe
CM Synergy
StarTeam

- testedsupported

 - added and tested by users

- added, but not tested in real-life

- tested, but not working
- not implemented

Features

This plugin collects information from SCM.

SCM Metrics in filter results

Image Removed

Dashboard widget

Image Removed

Source code viewer

Image Removed

Usage & Installation

...

SCM information on each source file to display in the source code viewer the last committer on lines.

Image Added

Installation

1. Install the SCM Activity plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
2. Restart the Sonar server

Usage

Configuring the SCM Activity Plugin

1. Set the SCM URL of your project (see SCM URL Format)

   .
   Example for Maven pom.xml

   :

   Code Block

   xml,title	pom.xml

   <scm> <connection>scm:svn:http://svn.codehaus.org/

   sonar

   -plugins/trunk/scm-activity</connection> <developerConnection>scm:svn:https://svn

   .

   codehaus.org/sonar-plugins/trunk/

   scm

   -activity</developerConnection> <url>http://svn.sonar-plugins.codehaus.org</url> </scm> Or you can use Project Setting - SCM URL.
   Or specify it via property sonar.scm.url.Go to Global/Project Settings
2. Enable plugin. This plugin disabled by default, because can dramatically increase analysis time of your project
Specify

.url properties. For Git, SVN and Mercurial, the SCM provider is automatically discovered, so what's defined in this property is not taken into account.

3. At project level, go to Configuration > Settings > SCM Activity and specify User (sonar.scm.user.secured) and Password (sonar.scm.password.secured) if needed; if specified then developerConnection will be used, otherwise connection.
4. Launch a new quality analysis and the metrics will be fed.

...

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

Add following to .subversion/servers:

[global]
ssl-authority-files = /path/certificate.crt
ssl-trust-default-ca = yes

CVS anonymous access not working "org.apache.maven.scm.ScmException: password is required."

Try to set empty password for repository in .cvspass. For example:

/1 :pserver:anonymous@javacaltools.cvs.sourceforge.net:2401/cvsroot/javacaltools A

Changelog

Release 1.4

I use Git and the annotated sources sometimes display a wrong/old author name

The plugin uses 'git blame' command to find out the author of each line. Because a user can commit with different author name/email, it is advised to have a .mailmap file at the root of the repository. This file is used by 'git blame' to find out canonical name/email of each user.

See http://git-scm.com/docs/git-blame#_mapping_authors

I use Git and the annotated sources sometimes display "Not Committed Yet"

In case you have set the parameter autocrlf to "true" or "input" and source file was previously committed with Windows line endings then git blame will report each line as "Not Committed Yet" as an indication that the file will be normalized to Unix line endings in case you do a modification and a commit on the same file.

The simplest workaround is to always set autocrlf to "false" on the box doing the Sonar analysis.

Change Log

...

...

...

Release 1.2

See  

...

...

...

...

...

...

...

...

...