Hi Ben, Thanks for your interest in helping out with the Flume project. I have created an infrastructure request [1] to enable this. Please add your comments and suggestions to that issue as necessary.
Regards, Arvind Prabhakar On Wed, Jun 20, 2012 at 1:25 PM, Ben Hardy <[email protected]> wrote: > Hello! New person delurking. > > I was chatting with Mike Percy after bumping into him at Hadoop Summit last > week, and we were discussing the idea of having test coverage and defect > analysis displayed in Flume's Jenkins page on https://builds.apache.org/ > > Effort-wise, this would be pretty easy for the Apache Infra team to do > since a Sonar server is already available at https://analysis.apache.org/ > - and Sonar is great, it provides really useful detailed information on > various code quality metrics (complexity, violations, dependencies, > findbugs, test coverage) in addition to showing graphs of how these metrics > change over time- so you can easily see at a glance the positive impact (or > not) changes have on code. It can also do hotspot drilldowns to show > problem areas Well worth a look. > > The Jenkins administrator need only: > - install Jenkins plugins for Sonar and Cobertura (if they haven't > already), > - configure the Sonar plugin with the JDBC connection details for the > existing Sonar server > - configure Jenkins Flume project page to enable Sonar and Cobertura. Sonar > will use Jenkins sonar setup, Cobertura usually has to be told to use its > default report pattern of "**/target/site/cobertura/coverage.xml" for maven > projects. > > This can make it easier to know where more test coverage and/or refactoring > could be most useful. > > cheers! > b >
