Re: Suggestions on Deploying Perl Test Environment

Well, I'd suggest looking into using many virtual machine environments to reduce hardware costs a bit. And yes, to test well, you'll need every environment available to test against.

We're currently using TeamCity as our automated build tool, but there are many other build tools out there.

-Scott

Comment on Re: Suggestions on Deploying Perl Test Environment

Replies are listed 'Best First'.
Re^2: Suggestions on Deploying Perl Test Environment by diabelek (Beadle) on May 12, 2008 at 17:03 UTC
Unfortunately we're hardware testing so we need direct access to the hardware as the parent/hypervisor sees it. We do some virtual machine testing as well so that is a good suggestion for when we tackle that area of automation.	[reply]
Re^3: Suggestions on Deploying Perl Test Environment by dmorgo (Pilgrim) on May 13, 2008 at 02:36 UTC
I don't know how feasible this is, but one idea I've toyed with is doing all the installation and configuration except for the last steps (whatever steps you are testing) on a VM machine, then making an installable image of that machine and installing it onto the real hardware for the final work. It should be bit-for-bit identical to an install done directly onto the hardware, as far as I can work out. Then do your final installation and testing. If anything goes wrong with the configuration, you presumably will have been smart enough to have done snapshots along the way of your VMs (at various steps during the preparation) and you can just roll back to any snapshot if you need to, then fix things and push it back onto the metal. Only problem with this is that I haven't actually done it, so I don't know for a fact that it works. It just seems like it should work.	[reply]