I have CruiseControl.net set up to run MSBuild and NUnit on my web application and then deploy it to a staging server.
Since NUnit doesn't have an Assert.IsNotUgly() method yet I need to look at the site on the staging server before deployment.
What would be great would be to use Cruise Control to handle the deployment from the staging to production servers using FTP. I know that this can be done as part of the build process, but I'd like to have a two step process that would require QA to go into the interface first and manually click a "Deploy to Production" button.
Is this possible/easy with CruiseControl.net?
John
Best Answer
Yes, basically you want two projects the first being the continuous or compile project, that would probably be interval trigger. The second project you would use an empty trigger block on (this means force build only) and this one would only handle the deploy logic.