Geek Answers Handbook

Cruise control in a virtual machine

Any downside to using Cruise Control in a virtual machine?

My build system is configured to look like

Machine 1: source code repository and server Machine 2: A virtual machine will be hosted. This virtual machine will host the virtual server, which in turn will serve the CruiseControl.Net server.

Any obvious flaw in this?

I could consolidate Machine 1 and Machine 2. I am a fan of the virtual installation for CI so that I can spawn multiple instances of spikes (fork testing projects)

Who has experience?

+4
source share
2 answers

There are no problems that I know of. We run CI on Amazon VM without any problems. Setting permissions, etc., is likely to be your biggest problem.

+1
source

No, which I know about ... for now. I recently installed our build server on VMWare VM, and still behaved just fine. One thing I did to relax in the configuration was to create a domain account (we are a Windows store) and use this domain account for all things related to my VM CruiseControl.Net server. This includes using it as the CruiseControl.Net service ID and control panel web application in IIS.

0
source

More articles:


All Articles