[M3devel] Tinderbox should always run tests?

[Jay K]

Next question -- how to get the tests status to appear?
I see the sample at the end of defs.sh -- call main | logfilter | mail.
But how do integrate that with ./tinderbox-build cm3.build?
Call them both one after the other?

I don't see relevant tinderbox or cm3 in /etc/cron* /etc/cron*/* on birch.

 - Jay


----------------------------------------
> Date: Wed, 22 Jul 2009 19:00:12 +0200
> From: wagner at elegosoft.com
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: Re: Tinderbox should always run tests?
>
> Quoting Jay K :
>
>> Olaf, is there any reason every Tinderbox run shouldn't run the tests?
>
> We don't want to run them both after the release- and the lastok-
> build (to save resources). It should be no problem to adapt the
> scripts for any specific setup (like I did on birch).
>
> If you don't run the release build, you should of course add running
> the tests after the lastok build.
>
> Olaf
> --
> Olaf Wagner -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>