Our build process and server have been working amazingly. It runs 24/7 and continuously builds and deploys to our development and QA environments the moment new code changes have been committed to the repository.
Each night, a new Release Package gets built and is available to be deployment into our live environment. The package includes database and website changes.
We are using CruiseControl and MSBuild to handle our automated build process and PowerShell to teardown, recreate and deploy both website and database.
As I mentioned, everything is running very smoothly and even at this early stage of hosting a live environment we are able to deploy in a matter of minutes.
We have 3 versions running in production; test, alpha and live. We deploy to 'test' first so we can ensure the latest Release Package has deployed successfully before we clone 'test' and roll the cloned copy into live. The 'alpha' version will be used to give our playtesters sneak previews of what is coming down the line.
All three versions are available on the website, deployed to the same hardware and infrastructure setup. For us this is important, as it allows global access from anyone we wish to see the various versions and we are therefore experiencing the true performance that players out on the web will receive.