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 suggestion! Am Dienstag, 12. Februar 2013 18:05:01 UTC+1 schrieb 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 failed or not... > > This kind of trick helped me a lot when I didn't want to rely on old > plugins or my requirement was too custom... > > > On Tue, Feb 12, 2013 at 10:27 AM, Zigster <zigst...@gmail.com<javascript:> > > wrote: > >> 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-use...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- 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.google.com/groups/opt_out.
