Re: Continuous Integration for Perl

2009-04-21 Thread Michael Peters
Andy Lester wrote: I have something called smolderbot that I threw together that does the same thing. I'm sure I could post it if wanted. But the short answer seems to be "no, there's nothing that is general purpose enough for what you want." Maybe something like CruiseControl will do it, I

Re: Continuous Integration for Perl

2009-04-21 Thread Andy Lester
On Apr 21, 2009, at 9:29 AM, Elizabeth Cortell wrote: I do just this. As part of a CI/test framework for my $job, I've written a script that runs a given suite then uploads to Smolder. I pull over the most recent svn changes with one cron job, then run the various suites against the cha

Re: Continuous Integration for Perl

2009-04-21 Thread Elizabeth Cortell
Smolder is great for the reporting of test failures. All you really need to do is create a TAP archive and send it to a Smolder server and it can send emails to your team or give you an RSS feed to pull from too. Creating a TAP archive is really easy if you use TAP::Harness::Archive (or if

Re: Continuous Integration for Perl

2009-04-21 Thread Michael Peters
Saftoiu, Rares wrote: I was wondering if there were any tools available for doing continuous integration with perl. I basically need something that will watch a directory, merge any branches from the directory into trunk, run unit tests, and email the committer in case of a merge conflict or fai