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

Configuration of continuous build integration in VSTS


Once the build definition is created, we will configure the Maven task to give the path to pom.xml so build definition can use pom.xml, to compile the source code and create a package file.

Select Maven pom.xml. In the Maven POM file, give the path to pom.xml for the existing project:

Click on the ... icon to browse through the folders available in the existing project and select the path to pom.xml:

Scroll down; in our case, select pom.xml and click on OK:

In the case of Maven, there are different goals such as compile, test, and package. We will give package here. If the default goal is available in pom.xml, then we don't need to explicitly mention it here. 

Keep the Test Results Files setting as it is:

Select Copy Files to: tasks and keep Source Folder and Target Folder as it is. In the Contents box, enter **/*.war. It will copy the WAR file available in the source directory of the project from any path and copy it to the staging directory...