Your browser does not support iframes.
Compatibility matrix
All SCM providers currently require the native executable to be installed on the box. For example svn.exe must be available in PATH for Subversion projects.
Plugin |
0.1 |
0.2 |
1.0 |
1.1 |
1.2 |
---|---|---|---|---|---|
Sonar |
1.12+ |
1.12+ |
2.0+ |
2.0+ |
2.7+ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Accurev (see SONARPLUGINS-455) |
|
|
|
|
|
- tested
- added and tested
- added, but not tested in real-life
- tested, but not working
- not implemented
Features
This plugin collects and reports information from SCM.
SCM Metrics in filter results
Dashboard widget
Source code viewer">Source code viewer
Code Coverage on New/Changed Code
Monitoring code coverage is crucial to understand the risks associated to making changes to an application. But when dealing with a big application with low coverage, you will also want to separate new code from old (based upon a given cut-off date) in order to track the new code which does not have any/enough unit tests.
This feature is available since Sonar 2.7 and SCM Activity plugin 1.2.
Live examples
To see live examples, you can browse following projects on Nemo:
- Git - Sonar
- Subversion - Sonar Plugins
- CVS - Java Calendar Tools
Usage & Installation
- Install from Update Center or download the JAR into the directory /extensions/plugins/
- Restart Sonar
- Define the SCM URL of your project (see SCM URL Format).
Example for Maven pom.xml :Or you can use Project Setting - SCM URL.<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 specify it via propertysonar.scm.url
. - Go to
Global/Project Settings
- Enable plugin. This plugin disabled by default, because can dramatically increase analysis time of your project
- Specify User (
sonar.scm.user.secured
) and Password (sonar.scm.password.secured
) if needed; if specified thendeveloperConnection
will be used, otherwiseconnection
- Launch a new quality analysis and the metrics will be fed
Known problems and limitations
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.2
See [Sonar 2.7 Upgrade Notes]