One of the most important measures of dbuild's and community build success is lines of code being covered. The cloc tool lets you count LoC easily.
It would be great if dbuild could run cloc for each project it builds. Even more awesome would be cumulative stats printed at the end of dbuild run which show total LoC covered.
Workaround
Current workaround is to run cloc tool manually. Go to community-build's checkout, and then to target-0.9.1/extraction/<latest_sha1>/projects. The <latest_sha1> is printed by dbuild and its a sha1 of unique configuration dbuild is about process.
Once in projects directory, run cloc . and get this:
One of the most important measures of dbuild's and community build success is lines of code being covered. The cloc tool lets you count LoC easily.
It would be great if dbuild could run cloc for each project it builds. Even more awesome would be cumulative stats printed at the end of dbuild run which show total LoC covered.
Workaround
Current workaround is to run cloc tool manually. Go to community-build's checkout, and then to
target-0.9.1/extraction/<latest_sha1>/projects
. The<latest_sha1>
is printed by dbuild and its a sha1 of unique configuration dbuild is about process.Once in projects directory, run
cloc .
and get this:Notice we cover over 1.2 million LoC of Scala! Celebrate by watching :fireworks: and sipping a :cocktail:!