Developer Activity Plugin

© 2008-2017, SonarSource S.A, Switzerland.
Except where otherwise noted, content in this space is licensed under a
Creative Commons Attribution-NonCommercial 3.0 United States License.

SONARQUBE is a trademark of SonarSource SA.
All other trademarks and copyrights are the property of their respective owners.

Ideas

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

Bruce Lowe

Sounds like you are looking to do something like fisheye. It may be worth checking its feature set out and seeing which are easily implemented based on the data that SVN/CVS gives you. (I wrote a simple program once that interacted with an SVN repo to see how many lines of code I had checked in etc. I cant remember where i put it, and its not extremely accurate).

I'd imagine you'd need to record the revision number per sonar build and see what changes happen per build.

Useful things might be

1. An "activity of the project" measurement (useful for seeing on the project view to see old/new projects) - based on either number revision changes, file changes or lines changed per time unit (e.g. day)
2. lines changes per time unit (e.g.day/week/month) by project and by user (to see active projects and who is contributing the most)
3. last N files changed list, who checked them in, their revision number, and a length limited comment. (maybe: Which can be clicked on to see the diffs)

Compatibility matrix

Description / Features

TBA

Usage & Installation

TBA

Known limitations

TBA

Troubleshooting

TBA

Changelog

TBA