Berin Loritsch wrote:
<snip/>
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.
this requires knowledge of what is important stuff and what is not. At the moment, gump just leaves the results of running ant where you put them, sometimes copying some of those results if you tell it to. Note you'd need a lot of RAM -- some projects are quite big :D
Well, I was thinking more like this:
GUMP defines what is exported like JAR files, JavaDocs, etc. and places them on the "archive" location which would be on a hard drive. One build at a time is placed in the "work" location (in the /tmp dir mapped to a RAM drive). When the build is finished and the results are archived, the work area is cleaned.
At any one time only so much space in the "work" area would be used.
This provides the best balance of hard drive thrashing and performance as things are built.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
