This project has moved. For the latest updates, please go here.

How do we run on TFS Build Server

Sep 9, 2013 at 9:14 PM
Do we just use the stored Xaml as the process template when running from the build server?
Sep 10, 2013 at 2:24 PM
The DevOps Workbench can be considered as a post build activity that specifically focuses on deployment activities. The Xaml generated from the Devops Workbench is intended to be executed from the Workbench itself or the Visual Studio add-in Workbench Explorer. Once you have created the desired deployment orchestration you can deploy/execute that orchestration to one the target servers(Tools menu option).

Are you interested in the ability to automatically trigger a defined deployment orchestration as part of a TFS Build?
Sep 11, 2013 at 6:10 AM
Running deployment orchestration as part of a TFS Build would be a really nice feature
Sep 13, 2013 at 6:15 AM
Currently we use in our company a custom autodeploy procedure based on a bunch of (PowerShell) scripts. This autodeploy procedure is triggered as the last build of our nightly build sequence and will deploy (after verifying all builds / unit tests are succeeded) our applications (IIS, SQL, BizTalk and console / Windows Services) to the specified servers of our Dev (multiple environments) or Test environment. Installation in our staging and production environment is a manual process (log in on server and use the same scripts for deployment).

At the moment we are evaluating the possibilities to improve our deployment process. Besides Visual Studio InRelease this project looks interesting. Automatically triggering a deployment orchestration as part of a TFS build is essential for us for Dev and Test environments because we deploy them daily / weekly. For staging and production environments is it a nice to have because installation in these environments is done by our operations department.