How long does it take to have a GUMP run go?
The reason I ask is that the approach for the http://cvs.apache.org
site would work if there were one or two continuous integration
machines, and the build results were rsync'd over to the serving
machine.
In an ideal world, I would like to be able to get GUMP build results
every four hours. The major problems with that approach are the
major thrashing of the hardware (hard drive wear and tear) and access
to hardware dedicated for the purpose. The major advantages are that
the hardware does not need to be serving internet content, and can
make connection only when it needs to rsync the results.
I guess a corrolery to the question of how *long* the build takes is
how much space do the builds take? Such a continuous integration
machine can save a lot of time and hardware thrashing if it used a
RAM drive to do the actual builds--since we are only interested in
the results anyway. Perhaps use the /tmp directory bound to a RAM
drive and do individual builds there, extracting all the important
stuff and then clearing out all the build byproducts we don't need.
Of course this defeats the purpose of getting GUMP to work on any
one person's machine.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
