Re: build system..

On Thu, 2002-01-31 at 10:29, Markus Fischer wrote: > On Thu, Jan 31, 2002 at 10:15:25AM +0100, Robin Ericsson wrote : > > Maybe we should construct some sort of build system al'a tinderbox? > > > > > > Roxen on the other hand has a nice pice tinderbox lookalike, which syncs > > the build between the machines, so all machines build on the same > > checkout, and after that, wait until all have been completed. > > > > This could be kinda nice to see what extensions etc, breaks on which > > platform/arch, based on checkins, and also opens for developers not > > having that many platforms (I got one ;) > > > > > > So, shoot me now please :) > > *peng* > > No, but I'm (+1) for this. > > Maybe it's worth we outline the things it should do in some > more detail? Maybe something like this: check "master" if "continue" retrive revision/tag/branch to checkout checkout/update php checkout/update Zend TSRM configure with as many extensions as possible compile, and register errors/warnings report back to master else wait > Btw, do you know how they sync the process ("wait until all > have been completed") ? Quoted from http://community.roxen.com/developers/autobuild/ "Unlike many other AutoBuild systems, our build clients doesn't continually. First of all they only compile a new build when the source code is changed, but they also wait for each others. That way all the builds are against the same source code, thus making it more easy to compare them and find bugs. If a build is successful and successfully verified it will be available for download, unless that build is restriced in some way." Technically I guess there is sort of "parent"-process which the machines included in buildsystem contacts to either checking/check what to/, etc.. and that parent know the status of it's children. regards robin