Book Image

Implementing CI/CD Using Azure Pipelines

By : Piti Champeethong, Roberto Mardeni
5 (1)
Book Image

Implementing CI/CD Using Azure Pipelines

5 (1)
By: Piti Champeethong, Roberto Mardeni

Overview of this book

Continuous integration and continuous delivery (CI/CD) are ubiquitous concepts in modern development. Azure Pipelines is one of the most popular services that you can utilize for CI/CD, and this book shows you how it works by taking you through the process of building and automating CI/CD systems using Azure Pipelines and YAML, simplifying integration with Azure resources and reducing human error. You’ll begin by getting an overview of Azure Pipelines and why you should use it. Next, the book helps you get to grips with build and release pipelines, and then builds upon this by introducing the extensive power of YAML syntax, which you can use to implement and configure any task you can think of. As you advance, you’ll discover how to integrate Infrastructure as Code tools, such as Terraform, and perform code analysis with SonarQube. In the concluding chapters, you’ll delve into real-life scenarios and hands-on implementation tasks with Microsoft Azure services, AWS, and cross-mobile application with Flutter, Google Firebase, and more. By the end of this book, you’ll be able to design and build CI/CD systems using Azure Pipelines with consummate ease, write code using YAML, and configure any task that comes to mind.
Table of Contents (18 chapters)
1
Part 1:Getting Started with Azure Pipelines
6
Part 2:Azure Pipelines in Action
11
Part 3:CI/CD for Real-World Scenarios
15
Chapter 12: Navigating Common Pitfalls and Future Trends in Azure Pipelines

Building and packaging applications and IaC

The applications in this solution are all container-enabled, a standard packaging mechanism that includes all operating system dependencies to allow them to run in many different hosting environments, making them extremely lightweight and portable.

For simplicity, the repository includes a docker-compose.yml file, which facilitates working with applications made of multiple services that must run at the same time.

This file defines the services and the location of their corresponding Dockerfile, the file that defines how the container must be built, and several other things, such as the ports or environment variables needed for the container to run.

In this chapter, the SUB_ID placeholder is the ID of the Azure subscription you have access to; make sure to replace it when appropriate.

Before you can proceed, you must have an Azure Container Registry available for the pipeline to store the container images. You can create one easily...