03 | Continuous Deployment James Chambers | Microsoft MVP in Asp.Net/IIS Tejaswi Redkar | Author, Director of Business Programs (AppPlat)

Module Overview A Bit of Background… Understanding the Internal Deployment Engine Visual Studio Online Integration Git Integration Exploring a Continuous Integration Strategy

Why Use Continuous Deployment? Compliments automated testing Rapid delivery to test environments Lowers risk as part of a CI strategy

Role for Windows Azure Web Sites With CD start simple code smart go live

Start Simple Easily create new sites Manage and scale your sites as required, or via automated means Automatic load balancing and shared storage across instances Ideal target for test environments, too!

Code Smart Use the language and tooling of your choice Use your SCM as a gateway with automated testing Trigger deployments from a simple check-in

Go Live “Hands off” or “Hands on” deployment Integrated source control with Team Foundation Server (TFS), Git, Mercurial and popular DSCM services Benefits of management, monitoring, reliability and scalability over self-hosted environments

Supported Publishing Methods 11/20/2018 Supported Publishing Methods FTP:// TFS WebDeploy DropBox © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

OOB Supported Service Hooks 11/20/2018 OOB Supported Service Hooks © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

What’s Happening in the Background? Kudu – an internal deployment engine – “watches” for check-ins An automated build is completed KuduSync kicks in The deployment is created in your website’s folder structure The new deployment is copied to your site’s root, leaving old deployments intact

More on Kudu It’s an open source project available on GitHub Automatically installed on all Windows Azure Web Sites Can use a custom deployment script

Exploring a Visual Studio Online Deployment

Using GitFlow

Deployment Sugar – Service Hooks Executed whenever a deployment via Git, Mercurial or DropBox is completed Retrieved from your configuration settings in the dashboard Can participate in trigger-action scenarios

Module Summary Looked at when to use continuous delivery and why you would Considered the tech, tools and options in play Examined a couple of scenarios with hosted SCM