Andy Lester wrote:
But the short answer seems to be "no, there's nothing that is general
purpose enough for what you want."
I talked about this missing piece at YAPC::NA this year and found some
interested parties who would like to work on such a project. We've have the
beginnings of a plan
A "bzr push" actually creates a new branch within the repository. I'm not
sure what notification facilities, if any, bzr has, so that's a good idea
for something to look into.
On 4/22/09 4/22/09 1:21 PM, "Michael G Schwern" wrote:
> Saftoiu, Rares wrote:
>> Smolder sounds great for viewing the r
Saftoiu, Rares wrote:
> Smolder sounds great for viewing the results, I was looking for something
> that could deal with branches. We branch on every bug fix, and then when the
> fix is done we push that branch to a particular directory, so at the end of
> a bug fix cycle we have a bunch of branche
On 4/21/09 4/21/09 7:32 AM, "Michael Peters" wrote:
> 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 enoug
On 4/21/09 4/21/09 5:01 AM, "Michael Peters" wrote:
> 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 un
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
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
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
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
Hi there,
2009/4/21 Saftoiu, Rares :
> 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
Hi,
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 failed unit test.
Any
11 matches
Mail list logo
