On Sun, Feb 18, 2001 at 11:33:52PM +0000, Nicholas Clark wrote:
> On Sun, Feb 18, 2001 at 06:26:00PM -0500, [EMAIL PROTECTED] wrote:
> > I'd like to set up automated daily build and smoke tests for bleedperl
> > and the other active trees.
>
> How many configuration permutations were you proposing?
I'm not so much worried about configuration permutations (yet) as
architectures and the particular configurations of our user's machines
(ie. utilities, libraries, compilers, etc...). Dealing with lots of
different configs both complicates the process and makes it much more
stressful on the smoker's machines.
This is sort of an easy way to say "Hey! If you want perl to work on
your machine, test it!" Consider it an easy and attainable step one.
> > It will be fairly simple to write and distribute a cron job which
> > wraps "make test" and emails if anything fails.
>
> For multiple configurations some sort of summary analysis really is necessary
> (although H Merjin Brand seems to have put a lot of effort into getting this
> completely under control)
Am I duplicating effort here?
