We are currently having a discussion in our team. We want to introduce code metrics (using Resharper command line tools => InspectCode). We generate reports (all working fine), but…
I have the feeling that people simply won’t look at the reports because there is no call for action (people only look at the build server to start a build or check what went wrong). So my idea was to break the build when code inspections show warnings. However, that might be too harsch for the team.
Our idea is to introduce warnings (or even allow a metric system with a % progress bar). These will make a build orange meaning there is room for improvement, but the build is successful.
How do you feel about this?
Hi Geert,
Thanks for these feature ideas.
Looks like we need to add an action for the InspectCode tool. I’ll add that to the to-do list.
We like the idea of having an orange warning status. This could be set via an action such as the the Log Entry action. I’ll investigate how easy it would be it implement this.
There is currently a way to generate custom metrics from external programs by writing @@continua[metric name=‘UnusedMember.Global’ category=‘InspectCode’ value=‘2’] to stdout. However, we only report on the ones that we recognise such as unit test metrics. We’ve been thinking that we could provide a way to display these values as a configurable custom indicator, probably on the left hand side of the build page.
Sounds good. Let me know if I can help you test anything once you have implemented this.