I've configured TFS 2010 to do a build and utilizing the MSBuild arguments, have it deploying to a single server without any issues.
/p:DeployOnBuild=True
/p:Configuration=Development
/p:DeployTarget=MSDeployPublish
/p:MSDeployPublishMethod=RemoteAgent
/p:MsDeployServiceUrl=http://<insert>/msdeployagentservice
/p:username=<insert>
/p:password=<insert>
However, I am now to the point where I'd like to deploy to multiple machines after a build. I wasn't sure if there were some built in mechanisms for doing this, or should I invoke a process to launch a batch file that does this deployment followed by a sync? I was hoping to keep things neat and tidy.
E.g., I could have two build definitions, one for each server, but that seems silly. I was hoping to just build to both servers in one fail swoop without too many outside customizations.
As of TFS 2010 you can customize your build process using the build definition template, this is a much richer way of configuring your build process. Is there a specific reason why you're not using this?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With