I'm working to upgrade our CI system with CruiseControl, MSBuild and MSDeploy. I've created separate build configurations for each stage of our web site, and set up MSBuild to run the following command to build the web package:
C:\...\MSBuild.exe C:\...\xxx.csproj /target:Package
This gives me the xxx.zip file and the xxx.deploy.cmd file, along with the additional xml files.
I want to be able to use the configuration from the project settings as much as possible, mostly for the version control safety blanket that it provides. Because of this, I'd like to be able to use that msbuild command and the xxx.deploy.cmd file with the least possible amount of modifications.
The problem I'm running into is that I don't know how to deploy that package to a different machine. Ultimately this process will take place on our build server, but needs to install the web package to our production server.
I'm aware of the computerName property that you're supposed to be able to use to specify the destination machine, but can't seem to find a standard way to append that property to the -dest: argument within the xxx.deploy.cmd without wiping out the arguments that were already in place from the msbuild process.
Any suggestions? Am I going about this the wrong way?