At the end of every release we manually calculate the total code churn from the previous release using a free tool called http://cloc.sourceforge.net/ CLOC (Count Lines of Code), but my manager wanted to know if this possible/feasible *per build*. CLOC gives you the total lines of code in a directory, and it allows you to diff it to another directory to see how much has changed between both directories (ie "you have 100 lines of code, 3 were added, 5 were modified, 10 were removed, from the previous release)
I'm looking into this, since when a build starts (from SVN or from Perforce), Jenkins knows what has changed from the previous build and we can get a diff report on what changed. I'm wondering if someone has done something similar, and has any pointers. We're using the https://wiki.jenkins-ci.org/display/JENKINS/All+Changes+Plugin All Changes Plugin , but it would be nice if there was a plugin that took this a step further and actually analyzed the data. I guess the poor man's way of doing it is to kick off a job when your build is done, and that job checks out the revision of the that job, *and *the revision of the previous job and does the diff. Thanks! -- View this message in context: http://jenkins.361315.n4.nabble.com/Calculating-Code-Churn-Per-Build-tp4633513.html Sent from the Jenkins users mailing list archive at Nabble.com.
