Continuous Deployment to an Azure Web App Deployment Slot

Sign in to queue

Description

In this Azure Walkthrough I cover how to set up a continuous deployment to an Azure Web Site with Deployment Slots.

You can learn more about setting up staging slots including slot settings and PowerShell commands for managing your deployment swaps at the following:

https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/

You can learn more about setting up Git for continuous deployment at the following:

https://azure.microsoft.com/en-us/documentation/articles/web-sites-publish-source-control/

If you need help learning Git, I suggest learn it by following along with the Git Immersion tutorial.

Embed

Download

Download this episode

The Discussion

  • User profile image
    sreekumar menon

    Thanks for the video on azure function slots.

    q: what happens to the staging slot after it is swapped? is it a throw away slot ? or will it be used for the next version(s)? or do we create new staging slots every time?

  • User profile image
    bsherwin

    @sreekumar menon:behind the scenes it's an IP swap, so it is still there...it's pointing to your previous version of the code. If something goes bad, you can swap it back in. When you are ready, deploy your next version of code over it and your ready to swap again. So it looks kind of like this...

    Prod = v1; Staging = v2...swap...Prod =v2; Staging = v1.

    Deploy v3 to Staging

    Prod = v2; Staging = v3...swap...Prod=v3; Staging = v2.

    Deploy v4 to Staging

    Prod = v3; Staging = v4...swap...Prod = v4; Staging = v3...(oops, deployed bug)...swap...Prod = v3; Staging = v4 

Add Your 2 Cents