DevOps for Azure Applications: Deploy Web Applications on Azure

by Suren Machiraju

Chapter 1: DevOps for Azure Chapter Traditionally, software development life cycle warranted siloed teams taking on specific tasks, i.e., Development Team and Operations Team wherein the Developers were responsible for writing code, checking in the source code into source control, testing the code, QA of the code and staging. The Operations/Production team was responsible for deploying the code to servers and thereafter coordinating with the customers and providing feedback to developers. Such siloed efforts were mostly manual processes with a small degree of siloed Application/Software deployment process. This manual process had several drawbacks and some of them are as No of pages 13 Chapter 01: DevOps for Azure ........................................................ 9-16 Need for DevOps ..................................................................................... 9 Describing the Functions of DevOps ..................................................... 10 DevOps Application Deployment Process............................................. 11 Understanding DevOps Tools ................................................................ 13 Chapter 2: Deployment via TeamCity and Octopus Deploy Chapter As discussed in the earlier chapter, an application deployment in DevOps requires a Continuous Integration (CI) tool and Continuous Delivery (CD) tool/release management software to automate the entire process. Currently, there are several such tools available in the market. In this chapter, we will use TeamCity as a CI tool and Octopus Deploy as a release management and CD software to get our package deployed on Azure Web Application. No of pages 28 Chapter 02: Deployment via TeamCity and Octopus Deploy .... 17-44 Introduction to Microsoft Public Cloud, Azure ..................................... 17 Understanding TeamCity ....................................................................... 18 Basic Concepts of TeamCity .............................................................. 18 Configuring Build in TeamCity ......................................................... 20 Creating a Package................................................................................. 27 Using Octopus Deploy ........................................................................... 30 Creating a Project ............................................................................... 31 Creating an Environment ................................................................... 32 Uploading NuGet Package to Octopus Deploy.................................. 34 Creating Steps for Deployment Process............................................. 36 Using Variables .................................................................................. 39 Creating and Deploying a Release ..................................................... 40 Summary ................................................................................................ 43 Chapter 3: Deployment via VSTS Chapter In the earlier chapter, we learned the process of deploying Applications to Azure through different on-premise tools. We used TeamCity as CI tool and Octopus Deploy as CD tool. The major problem with the earlier solution was that there was need of separate tools to deploy Applications. VSTS is a collaborative solution that takes care of the entire software deployment lifecycle from creating packages to deploying the Application. In this chapter, we will go through the entire process of Application deployment to Azure using VSTS. No of pages

144 pages, Paperback

Published May 23, 2018

Reviews

[James · Rating 2 out of 5]

I didn't follow the steps to see how useful it is, but it explains how to set-up some specific tools (eg TeamCity, Octopus Deploy, VSTS) that you could use in an Azure context. Probably not useful for many who will have more specific requirements for their application. I thought it was a bit of an odd decision to often redact the screenshots. I can understand not wanting to show your username, but it often looked like they were redacting basic stuff like a repository name. You'd expect their repository to either be public so readers of the book can cross-reference what they have, or just delete it once the book launches.

[Alexander Müller · Rating 2 out of 5]

Too specific and too focused on just a few tools (TeamCity, Octopus Deploy, VSTS).
The chapters consist mainly of bulletpoints and some guiding screenshots. Not useful for developers who want to use it as a starting point for setting up a custom DevOps solution.

[Lolo · Rating 1 out of 5]

This is a small book that would have been a few articles in social media. I'm having difficulty finding useful things in this.

[Pham Tung · Rating 1 out of 5]

nothing useful

[Burnthevillages · Rating 1 out of 5]

Very specific and opinionated. Everyone isn't going to use the exact same tools.