Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 122 Next »

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+

Subversion

(plus)

(tick)

(tick)

(tick)

(tick)

Git

(plus)

(tick)

(tick)

(tick)

(tick)

CVS

(minus)

(plus)

(tick)

(tick)

(tick)

Mercurial

(minus)

(plus)

(tick)

(tick)

(question)

Bazaar

(minus)

(plus)

(tick)

(tick)

(question)

Perforce

(minus)

(minus)

(minus)

(plus)

(question)

StarTeam

(minus)

(minus)

(minus)

(minus)

(minus)

Team Foundation Server (see SONARPLUGINS-373)

(minus)

(minus)

(minus)

(question)

(question)

ClearCase

(minus)

(minus)

(minus)

(plus)

(question)

Accurev (see SONARPLUGINS-455)

(minus)

(minus)

(minus)

(question)

(question)

(tick) - tested
(plus) - added and tested
(question) - added, but not tested in real-life
(error) - tested, but not working
(minus) - not implemented

Features

This plugin collects and reports information from SCM.

SCM Metrics in filter results

Dashboard widget

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:

Usage & Installation

  1. Install from Update Center or download the JAR into the directory /extensions/plugins/
  2. Restart Sonar
  3. Define the SCM URL of your project (see SCM URL Format).
    Example for Maven pom.xml :
    Or you can use Project Setting - SCM URL.
    Or specify it via property sonar.scm.url.
  4. Go to Global/Project Settings
    1. Enable plugin. This plugin disabled by default, because can dramatically increase analysis time of your project
    2. Specify User (sonar.scm.user.secured) and Password (sonar.scm.password.secured) if needed; if specified then developerConnection will be used, otherwise connection
  5. 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:

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

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

Changelog

Release 1.2

See Sonar 2.7 Upgrade Notes

Loading

Release 1.2 (16 issues)

Release 1.1

Loading

Release 1.1 (4 issues)

Release 1.0

Loading

Release 1.0 (6 issues)

Release 0.2

Loading

Release 0.2 (8 issues)

Release 0.1

Loading

Release 0.1 (6 issues)

  • No labels