Reputation: 595
As mentioned in here :
https://www.windowsazure.com/en-us/develop/net/common-tasks/publishing-with-tfs/
The TFS code will be deployed to Staging Environment.
I'm wondering if we can do something in the TFS so that we can have option to deploy to Staging and/or Production Environment.
Many thanks !!!
Upvotes: 2
Views: 697
Reputation: 428
As Habibi says, you can swap the Staging and Production. Step 6 on this page: http://www.windowsazure.com/en-us/develop/net/common-tasks/publishing-with-tfs/
From step 6 description:
Applies only to cloud services, not web apps. When you are ready, you can promote the Staging environment to the production environment by choosing the Swap button in the Azure classic portal. The newly deployed Staging environment is promoted to Production, and the previous Production environment, if any, becomes a Staging environment. The Active deployment may be different for the Production and Staging environments, but the deployment history of recent builds is the same regardless of environment.
Upvotes: 0
Reputation: 41
You can set the Alternate Cloud Service Environment property in the build definition in order to customize "Staging" or "Production" as the default. The default when this property is not set will be "Staging".
Upvotes: 4
Reputation: 20556
From TFS perspective there is no distinction between staging or production because TFS will deploy where ever you would configure it to publish.
When you use Windows Azure Cloud Services, you can choose Staging or Production slot while configuring your Azure TFS and this way your TFS project will always deploy to configured slot.
Upvotes: 0