Not much. If you only run a single build, it is pretty much dependent on the amount of memory you need for your build itself. Disk space can be controlled by proactively clearing out old build dirs/logs/etc. We've successfully run VMs of real rails app builds with only 256M of RAM. Of course, you want to keep an eye on that and ensure that neither the virtual machine nor the host OS is swapping.
Bottom line, just try it out and keep a close eye on disk space and memory on both the host OS and the virtual machine. One caveat - Cruise.rb runs a separate builder process for each project. So, multiple projects - especially if you run them concurrently - can really bog down the VM. Even if you don't run them concurrently, you still need more memory for each additional project. Hope this helps. Good Luck, -- Chad On Sun, May 25, 2008 at 2:10 PM, Lori Olson <[EMAIL PROTECTED]> wrote: > Does anyone have any feel for the requirements (disk space, memory, anything > else you can think of) of a virtual machine (say Centos Linux), set up as a > CruiseControl.rb build machine? > > Regards, Lori > > _______________________________________________ > Cruisecontrolrb-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
