New Azure To TFS Deploy Tool Available

Deploy Windows Azure project directly from TFS 2010 Build Server

 

DeployToAzure allows automating deployment of Windows Azure project and making it a part of TFS 2010 build process without using PowerShell and Azure Management CmdLets.

Solution includes:

• A set of custom workflow actions wrapping Azure Management API operations such as GetDeployment, GetOperationStatus, NewDeployment, RemoveDeployment and SetDeploymentStatus;
• Helper actions such as FindPackageAndConfigurationFiles, LoadCertificate and WaitForOperationToComplete;
• Designer activity DeployToAzure implementing deployment logic ;
• Reusable build definition template.

How it works :

Create build definition

Open New Build Definition dialog. Select Process tab. Click New button in Build process template section. Choose Select an existing XAML file option and specify path to DefaultTemplateWithDeploymentToAzure.xaml in your source control.

Deployment to Azure section will appear in Build process parameters. Click Refresh button if you don’t see it.

Now define build properties. First ,open 1. Required / Items to build dialog and select your solution and specify configuration to build.

Open Deployment to Azure section and provide following parameters:

• API Certificate store location – store location of your management certificate. Select LocalMachine if certificate was created by command above.
• API Certificate Thumbprint – thumbprint of management certificate.
• API Certificate store – store where management certificate is located. Select Root if certificate was created by command above.
• Cloud Project – cloud project to be packaged and deployed.  It will be built with the same configuration as the one specified for solution building.
• Deployment label – label of deployment. Label can contain same set of macros as Build Label.
• Hosted Service Name – DNS Prefix of Hosted service. You can find it on Windows Azure portal.
• Service configuration – service configuration to be used for deployment, for example Cloud. Keep this field empty to use default configuration.
• Slot – select Staging or Production.
• Storage Service Name – DNS Prefix of storage service which will be used to upload deployment package.
• Subscription Id – Azure subscription ID.
• Wait for roles to start – set to true if build should wait for all instances to start.
• Initialization Timeout – if above is true, specify timeout for build to wait before generate timeout exception.

Contact me at floyd_tomas@yahoo.com for this and other Azure, SharePoint, Office365,  TFS and Agile Tools