Book Image

Azure DevOps Explained

By : Sjoukje Zaal, Stefano Demiliani, Amit Malik
Book Image

Azure DevOps Explained

By: Sjoukje Zaal, Stefano Demiliani, Amit Malik

Overview of this book

Developing applications for the cloud involves changing development methodologies and procedures. Continuous integration and continuous deployment (CI/CD) processes are a must today, but are often difficult to implement and adopt. Azure DevOps is a Microsoft Azure cloud service that enhances your application development life cycle and enables DevOps capabilities. Starting with a comprehensive product overview, this book helps you to understand Azure DevOps and apply DevOps techniques to your development projects. You'll find out how to adopt DevOps techniques for your development processes by using built-in Azure DevOps tools. Throughout the course of this book, you'll also discover how to manage a project with the help of project management techniques such as Agile and Scrum, and then progress toward development aspects such as source code management, build pipelines, code testing and artifacts, release pipelines, and GitHub integration. As you learn how to implement DevOps practices, this book will also provide you with real-world examples and scenarios of DevOps adoption. By the end of this DevOps book, you will have learned how to adopt and implement Azure DevOps features in your real-world development processes.
Table of Contents (17 chapters)
1
Section 1: DevOps Principles and Azure DevOps Project Management
4
Section 2: Source Code and Builds
9
Section 3: Artifacts and Deployments
12
Section 4: Advanced Features of Azure DevOps

Handling a pull request

All the different ways to handle a pull request that we've described converge to a unique point: in Azure DevOps, the Pull requests window opens, and you need to fill in the details of your pull request activity. As an example, this is the pull request that we started after the previous commit on the development branch:

Figure 3.55 – New pull request window

Here, you can immediately see that the pull request merges a branch into another branch (in my case, development will be merged into master). You need to provide a title and a description of this pull request (that clearly describes the changes and the implementations you made in the merge), as well as attach links and add team members (users or groups) that will be responsible for reviewing this pull request. You can also include work items (this option will be automatically included if you completed a commit attached to a work item previously).

In the Files section...