# from Andy Armstrong
# on Monday 05 February 2007 10:27 am:
>I guess there are already frameworks
>available that'd help with managing that kind of distributed setup?
>The most similar thing I have any experience of is distcc[1].
>
>As a matter of interest I wonder if anyone's worked out whether
>Perl's build process plays nicely with distcc? A nice test case for
>distributed tests might be to start with a working distributed build
>process and then find a way of making the post-build tests
>distributed too.
From my reading, distcc only ships a single pre-processed file across
the wire and gets a binary back from the cc on the other end. That's a
very simple and easy to distribute scheme, and I think the claim is
that it will work in any build as a drop-in replacement for cc.
A similar scheme might work instead of the rsync (or nfs?) full-mirror
that I suggested, but it would basically mean shipping the entire
dependency tree across the wire, plus whatever arbitrary data might be
needed. I think this means it is best to setup the delegate boxen
beforehand. Either way, I'm not sure it really needs a different test
execution and reporting scheme than a locally parallelized build.
--Eric
--
But as soon as you hear the Doppler shift dropping in pitch, you know
that they're probably going to miss your house, because if they were on
a collision course with your house, the pitch would stay the same until
impact. As I said, that's one's subtle.
--Larry Wall
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
