Full documentation for SonarQube has moved to a new location: http://docs.sonarqube.org/display/SONAR

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 10 Next »

Name

Sonar SCM Activity Plugin

Authors

Evgeny Mandrikov

Jira

http://jira.codehaus.org/browse/SONARPLUGINS/component/14305

Latest version

0.1-SNAPSHOT

License

Apache 2

Sources

http://svn.codehaus.org/sonar-plugins/trunk/scm-activity/

Download

TBA

Compatibility matrix

Plugin

0.1-SNAPSHOT

Sonar

1.12+

Subversion

(tick)

Git (see SONARPLUGINS-329)

(minus)

CVS (see SONARPLUGINS-330)

(minus)

Mercurial (see SONARPLUGINS-331)

(minus)

Description / Features

TBA

Usage & Installation

TBA

Known limitations

TBA

Troubleshooting

TBA

Changelog

Loading

Release 0.1 (6 issues)

Ideas

See http://n2.nabble.com/New-Developer-Activity-Plugin-tp4240105p4240105.html

Evgeny Mandrikov

Looks like start point can be a maven-changelog-plugin or scmchangelog-maven-plugin.

I'm looking for simplest way of how to support all SCMs (see http://maven.apache.org/scm/scms-overview.html). SCMs in importance order:

  1. SVN
  2. Git

Metrics:

  1. Last commit
  2. Number of commits since last release (see http://n4.nabble.com/Unreleased-plugin-changes-tp990541p990541.html)
Chad Retz

I was going to attempt to do this as well. IMO, you should split the information into two types: ETL processed and live. Reason is, you can get so much information parsing the logs. Actually, you can just take the code from StatSVN and StatCVS, and translate something like GitStats to Java for the ETL portion. This should make your life much easier developing this, and give a lot more cool features.

  • No labels