Implementing Continuous Delivery
The course is part of this learning path
This course deals with how to implement continuous delivery with the Azure DevOps solution. In particular, we will be exploring how to design different release strategies and some factors you need to consider while setting up release pipelines. This will include looking at release triggers, release gates, and other areas associated with releasing code, including working with different environments. We will also take a look at deployment patterns and how they can be implemented in your release strategy and release pipelines. During this course, we will be using hands-on examples to help work through these concepts and configurations.
If you have any feedback for us about this course, please contact Cloud Academy at email@example.com.
- Design a release strategy
- Set up a release management workflow using Azure DevOps
- Implement an appropriate deployment pattern
- DevOps engineers
- People preparing for Microsoft’s AZ-400 exam
- General knowledge of Azure
- Experience with Git version control, including pushing changes into repositories
- You do not need to know any specific development language
You will hear continuous delivery is often combined with the term CI/CD or continuous integration, continuous delivery, but what is it? It was born as part of a manifesto to software development but has evolved over time and is used widely in various different ways. Wikipedia defines continuous delivery as "An approach in which teams produce software in short cycles, ensuring that software can be reliably released at any time and when releasing the software, doing so manually. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce cost, time, and risk of delivering changes by allowing for more incremental updates to an application in production. A straightforward and repeatable deployment process is important for continuous delivery."
Continuous delivery is made possible through the implementation of processes enabling a trusted and repeatable deployment pipeline. While manual triggers are often used to move through these different stages as a pipeline matures and the process itself gains trust, many of these triggers become automated, which we will look at during this course.
Matthew Quickenden is a motivated Infrastructure Consultant with over 20 years of industry experience supporting Microsoft systems and other Microsoft products and solutions. He works as a technical delivery lead managing resources, understanding and translating customer requirements and expectations into architecture, and building technical solutions. In recent years, Matthew has been focused on helping businesses consume and utilize cloud technologies with a focus on leveraging automation to rapidly deploy and manage cloud resources at scale.