Another approach would be to create a separate project that ran the test:coverage rake task, no? This project could have a time-driven trigger. Or it might run only when the other project's task isn't running.
Bret On Sat, Feb 21, 2009 at 1:32 PM, Alexey Verkhovsky < [email protected]> wrote: > On Sat, Feb 21, 2009 at 10:35 AM, Sebastian Nowak < > [email protected]> wrote: > >> Hello, >> I wonder if there is possible to do something like this: >> - on every commit CC execute rake test >> - once a day CC execute rake test:coverage > > > This sounds like a piece of logic that you can easily implement within the > Rake build. > > The idea with CC.rb is that it doesn't provide unusual fancy features - if > you need them, you either put it in the build or hack the tool itself. It's > rather simple, and written in an interpreted language. Therefore, easy to > hack. > > -- > Alexey Verkhovsky > http://alex-verkhovsky.blogspot.com/ > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > > > _______________________________________________ > Cruisecontrolrb-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > -- Bret Pettichord GTalk: [email protected] CTO, WatirCraft LLC, http://www.watircraft.com Lead Developer, Watir, http://www.watir.com Blog (Essays), http://www.io.com/~wazmo/blog MiniBlog (Links), http://feeds.feedburner.com/bretshotlist Training, http://www.watircraft.com/watir-training
_______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
