Re: Monitoring Metrics (eg. code coverage) Degradation

2013-02-13 Thread William Soula
Sorry I should have read the whole thread cobertura is java only :( Using some code coverage tool for php you might be able to transform those results to cobertura format, with XSLT or something, and then use the cobertura plugin. Will On 02/13/2013 03:10 PM, Zigster wrote: Thanks for the hint

Re: Monitoring Metrics (eg. code coverage) Degradation

2013-02-13 Thread Zigster
Thanks for the hint William! Does the cobertura plugin work with php and phpunit respectively? Thanks for info on that!! Zigster Am Mittwoch, 13. Februar 2013 16:20:49 UTC+1 schrieb William Soula: > > The cobertura plugin allows you to mark a build as unstable if the user > configured thres

Re: Monitoring Metrics (eg. code coverage) Degradation

2013-02-13 Thread William Soula
The cobertura plugin allows you to mark a build as unstable if the user configured threshold for the coverage metric falls below a certain percentage. Might even be able to make it fail. You could also use the build timeout plugin to abort the build after a certain amount of time, or a percent

Re: Monitoring Metrics (eg. code coverage) Degradation

2013-02-13 Thread Zigster
I figured, that this would be one way to do. It's a bit strange, that there's no plugin providing that feature as implementing a build fail for deteriorating code coverage or slow tests is mentioned in a few reputable books (just as "Continuous Delivery" by Humble/Farley) Thank you for your s

Re: Monitoring Metrics (eg. code coverage) Degradation

2013-02-12 Thread Octavian Covalschi
You may not like this solution, but until someone will post a better solution, you could potentially create a simple shell task and run your coverage metrics from there... With some magic you could check the results and return 0 or 1 (i'm not sure the exact value), which will tell jenkins if it fai

Re: Monitoring Metrics (eg. code coverage) Degradation

2013-02-12 Thread Zigster
It's a PHP project... -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.googl

Re: Monitoring Metrics (eg. code coverage) Degradation

2013-02-12 Thread Octavian Covalschi
What language are you using? On Tue, Feb 12, 2013 at 6:17 AM, Zigster wrote: > Hi, > > I'm trying to figure out, how to monitor the state of the code coverage in > a project. > > Therefore, I would want to let the build get marked as "failed" as soon as > the code coverage (or any other metric)

Monitoring Metrics (eg. code coverage) Degradation

2013-02-12 Thread Zigster
Hi, I'm trying to figure out, how to monitor the state of the code coverage in a project. Therefore, I would want to let the build get marked as "failed" as soon as the code coverage (or any other metric) drops from the previous build to the current. While browsing through the avalibale plugi