Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Continuous delivery with azure app service

463 views

Published on

How to harness the power of Azure App Service to provide continuous delivery pipeline.

Published in: Technology
  • Login to see the comments

  • Be the first to like this

Continuous delivery with azure app service

  1. 1. CONTINUOUS DELIVERY WITH AZURE APP SERVICE How to harness the power of Azure App Service to provide continuous delivery pipeline.
  2. 2. ABOUT ME  Director of Application Architecture at CarFinance.com  15 years of industry experience  Currently leading the cloud initiative at CarFinance.com  mnabeelkhan.blogspot.com
  3. 3. WHAT WE WILL COVER  Continuous delivery concepts  Power of App Services  Continuous delivery pipeline  Importance of Branching strategies  Steps for building the continuous delivery pipeline
  4. 4. WHAT IS CONTINUOUS DELIVERY?  Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. It aims at building, testing, and releasing software faster and more frequently. – Wikipedia.  In simple words “Constantly develop, automatically build and automatically deploy”. This means that as soon as code is checked in a system would automatically build the application and deploy.
  5. 5. POWER OF APP SERVICES Some of the advantages…  Unlike IIS, App service focuses on single app. Hence, the management of IIS has been abstracted away.  Easy to produce multiple hosting environments from click of button.  Unified security for different deployment slots.  Deployment-slot-based application settings.
  6. 6. A SET OF TYPICAL DEV. ENVIRONMENTS Dev. QA UAT Staging Prod.
  7. 7. ESTABLISHED DEPLOYMENT SLOTS EXAMPLE
  8. 8. ESTABLISHMENT OF BRANCHING STRATEGY Master branch – For Development environment QA Branch – For QA and UAT environments Production – For staging environment
  9. 9. SUPPORTED DEPLOYMENT MEDIUMS FTP Web Deploy Kudu
  10. 10. AND THEN THERE IS…THE APP SERVICE DEPLOYMENT
  11. 11. A WORD ABOUT SUPPORTED SOURCES Deployment source
  12. 12. HOW IT WORKS Code checked-in to Kudu initiates the build Kudu publishes the website
  13. 13. DEMO
  14. 14. WHAT ABOUT IF YOU HAVE MULTIPLE SITES IN ONE PROJECT
  15. 15. MULTIPLE WEB APPS CHALLENGE  Step 1. Add app setting to your App Service to uniquely identify your app. This is to give Kudu a way to kick start the build and complete the publishing once code has checked in.  Step 2. Add “.deployment” file to the base of your source code repository. The “.deployment” file gives Kudu a starting point to start the deployment process.  Step 3. Create deploy.cmd file. This is the file that would tell Kudu how many different web apps or web Api apps are available in your code base that needs to be built as part of continuous integration pipeline.
  16. 16. GENERATING DEPLOY.CUSTOMER.CMD  Step 1: Create site deployment script.  Step 2: Rename the deployment script output file to match your project.  Step 3: Repeat steps 1 to 2 for each project.
  17. 17. EXAMPLE DEPLOYMENT CODE
  18. 18. RESOURCES  mnabeelkhan.blogspot.com  http://blog.amitapple.com/
  19. 19. QUESTIONS

×