Book Image

Implementing Azure DevOps Solutions

By : Henry Been, Maik van der Gaag
Book Image

Implementing Azure DevOps Solutions

By: Henry Been, Maik van der Gaag

Overview of this book

Implementing Azure DevOps Solutions helps DevOps engineers and administrators to leverage Azure DevOps Services to master practices such as continuous integration and continuous delivery (CI/CD), containerization, and zero downtime deployments. This book starts with the basics of continuous integration, continuous delivery, and automated deployments. You will then learn how to apply configuration management and Infrastructure as Code (IaC) along with managing databases in DevOps scenarios. Next, you will delve into fitting security and compliance with DevOps. As you advance, you will explore how to instrument applications, and gather metrics to understand application usage and user behavior. The latter part of this book will help you implement a container build strategy and manage Azure Kubernetes Services. Lastly, you will understand how to create your own Azure DevOps organization, along with covering quick tips and tricks to confidently apply effective DevOps practices. By the end of this book, you’ll have gained the knowledge you need to ensure seamless application deployments and business continuity.
Table of Contents (21 chapters)
1
Section 1: Getting to Continuous Delivery
6
Section 2: Expanding your DevOps Pipeline
12
Section 3: Closing the Loop
15
Section 4: Advanced Topics

Identifying shared components

Adopting DevOps practices, such as continuous integration/continuous delivery, can greatly reduce the amount of time you have to spend on building and testing your applications. Besides building your applications, there are also many other concerns that you can address in your pipelines.

When you start adding more and more tasks to your pipelines, you might run into a situation in which a single execution of your pipeline starts taking too long, sometimes longer than 5 minutes. Note that this a general recommendation for the maximum duration of a CI pipeline. In order to battle this, you might be interested in splitting your solution up into smaller builds and maybe even repositories. To do this, you could build parts of that application in isolation and then use the results of these builds in your main application as ready-built components.

A general...