Matthew Willis wrote:
> This may not be necessary, but I had an idea today about having other,
> remote machines be able to participate in the build farm. A remote
> tester could set up a daemon on their own machine that would perform
> the same tests that are in your build farm. Even if those remote
> testers end up testing the same configurations as the build farm
> machines, it couldn't hurt to have more data, right? :)
Absolutely. The builder was designed for this in fact. Anyone anywhere can
participate in building, testing, and even creating binary packages for
Factor. This is how you do it:
$ ./factor -run=builder
That's it. If new patches are available or if a new boot image if available, a
build will kick off. The builder checks for new code every 5 minutes. If you
want to receive a report summarizing the build results, set the value
of 'builder-from', 'builder-recipients', and 'smtp-host'. I set these in
my ".factor-boot-rc". Mine looks like this (you'll have to add to your USING:
accordingly) :
----------------------------------------------------------------------
"[EMAIL PROTECTED]" builder-from set-global
{
"[EMAIL PROTECTED]"
"[EMAIL PROTECTED]"
"[EMAIL PROTECTED]"
} builder-recipients set-global
"factorcode.org" smtp-host set-global
----------------------------------------------------------------------
If anyone is willing to run a builder on a platform that we don't test
regularly, we'd probably be interested having you add us to
your 'builder-recipients' list. :-)
Ed
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
