SVN Statistics

[Gavin Beau Baumanis]

Hi Everyone,

I have been asked for some statistics about our code base and am hoping that someone might have had a task for something similar already, and will be able to help me out.

Here is the text I was sent - but it is really just a guide - it is more a case of "something" to show as opposed to have any specific item(s).

I do have a jar that I downloaded from SourceForge - that provides pretty much what I'm after.
Lines of code / Churn,
Number of commits etc.

But it is based on the entire repository from revision 0:head.

The specific request (below) comes from the point of view ;
These are stats are from rev xxx - when we started work on the latest version.

We don't have a classical "release" branch either - just a forever going trunk, so we can't use anything "path" specific to obtain the requested results either.

Anyway - if you have ideas - I would be most grateful, here is the questions I was asked;

Added xxx Lines of new code
Removed xxx Lines of redundant code
Performed more than xxx individual code changes.

As always - thanks very much in advance!

Gavin.

[Chris Evans]

It might be a bit overkill for what you're after, but Atlassian Fisheye is really good http://www.atlassian.com/software/fisheye/
It'll give you user statistics for LoC, commits etc. You can also set a starting revision rather than 0.

Chris

--------------
Gloucester Research Limited believes the information provided herein is reliable. While every care has been taken to ensure accuracy, the information is furnished to the recipients with no warranty as to the completeness and accuracy of its contents and on condition that any errors or omissions shall not be made the basis for any claim, demand or cause for action.
The information in this email is intended only for the named recipient.  If you are not the intended recipient please notify us immediately and do not copy, distribute or take action based on this e-mail.
All messages sent to and from this email address will be logged by Gloucester Research Ltd and are subject to archival storage, monitoring, review and disclosure.
Gloucester Research Limited, 5th Floor, Whittington House, 19-30 Alfred Place, London WC1E 7EA.
Gloucester Research Limited is a company registered in England and Wales with company number 04267560.
--------------

[Nick Stolwijk]

You could make a git clone of your Subversion repository.

git log --numstat shows the lines added and deleted per commit (revision).

Hth,

Nick Stolwijk
~Java Developer~

iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl

[Nick Stolwijk]

On another note, I see you have a jar from SF which does almost what
you want. Why not checkout their code and let it do exactly what you
want? I guess somewhere in there is a starting revision, which you can
change.

If you don't know Java, send me the projectname and I can have a look.

Hth,

Nick Stolwijk
~Java Developer~

iPROFS
Wagenweg 208
2012 NM Haarlem
T +31 23 547 6369
F +31 23 547 6370
I www.iprofs.nl

[Kevin Grover]

Check out StatSVN:

http://www.statsvn.org/

Cheers.

[Gavin Beau Baumanis]

Hi kevin,

This is indeed the stats package that I already have.

But it is a little sparse on documentation.

It has great statistics that are useful when I report on the whole project - but I have been unable to find a way to say,

Start at this Revision / in this path...

I did find this;

http://statsvn.1260.n2.nabble.com/forum/PostLink.jtp?post=5283797

Which I overlooked (that it actually uses the log you create, prior to running the jar) - but it does says that;

"the produced results are not the best since StatSVN assumes it knows all the data in the repository. "

The biggest issue I have really, is that I am not a java developer (not a SVN developer) for that matter.

So I really am unable to do it myself.

I'll give the svn log route a go and see how it works out.

[Kevin Grover]

Granted, the StatSVN documentation could be better - I had also looked for a way to exclude the twitter links, but just did not care enough. 

One possible solution for you may just be to use svnadmin dump and filter out what you want to report on (svndumptool could also be helpful for this).

Good luck.

[Richard England]

Another is svnplot   http://code.google.com/p/svnplot/