Our TeamCity builds generate .msi files as artifacts and the next step for us is to automate the deployment of these.
I want to separate the deployment from build configuration so adding deployment as build steps is out of the question.
Second, I could script something from a dependant project but it requires a VCS root.
Perhaps a deployment branch of the project containing only the scripts.
That could work if I wire up artifact dependencies.
I was wondering if anyone else here on the forums are doing the same and was willing to share some tips ?
The .msi files are both services, standalone applications and web applications. The difference should not really matter as the msi should take care of that.