Book Image

Implementing DevOps with Microsoft Azure

By : Mitesh Soni
Book Image

Implementing DevOps with Microsoft Azure

By: Mitesh Soni

Overview of this book

This book will teach you all about the Visual Studio Team Services and Microsoft Azure PaaS offerings that support Continuous Integration, Continuous Delivery, Continuous Deployment, and execution in the cloud with high availability, disaster recovery, and security. You will first be given a tour of all the concepts and tools that Microsoft Azure has to offer and how these can be used in situations to cultivate the DevOps culture. You’ll be taught how to use and manage Visual Studio Team Services (VSTS) and about the structure of the sample application used throughout the book. You will become familiar with the nitty gritty of Continuous Integration and Continuous Development with VSTS and Microsoft Azure Apps. You will not only learn how to create App service environments, but also how to compare Azure Web Apps and App Service Environments to deploy web applications in a more secure environment. Once you have completed Continuous Integration and created the Platform for application deployment, you will learn more about the final stepping stone in achieving end-to-end automation using approval-based Continuous Delivery and Deployment. You will then learn about Continuous Monitoring, using the monitoring and notification options provided by Microsoft Azure and Visual Studio Team Services.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
Acknowledgment
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
More from the Author

Creating a build definition for VSTS project


The objective of this section is to configure a code repository with VSTS in such a way that every time a developer checks in the code into the repository, it should automatically trigger the build script to execute and thus complete compilation, unit test execution, and SonarQube analysis (static code analysis), and notify different stakeholders based on the outcome of the CI process.

We should always remember that a process is always the same irrespective of the tools we use, be it open-source tools or commercial tools. We need build scripts; in case of a Java-based project, we need build.xml for Ant or pom.xml for Maven to execute the build. We need unit test cases written in JUnit or any other supported language. 

Before explaining the steps for CI, we need to understand and remind ourselves that the DevOps is a culture and combination of people, processes, and tools. It is not only about automation. It is also about mindset change, change in...