Define your Classic pipeline

Define your Classic pipeline

Azure Pipelines provide a highly configurable and manageable pipeline for releases to multiple stages such as development, staging, QA, and production. it also offers the opportunity to implement gates and approvals at each specific stage.

In this tutorial, you will learn about:

• Continuous deployment triggers
• Adding stages
• Adding pre-deployment approvals
• Creating releases and monitoring deployments

Prerequisites

You'll need:

• A release pipeline that contains at least one stage. If you don't already have one, you can create it by working through any of the following quickstarts and tutorials:

  • Deploy to an Azure Web App
  • Azure DevOps Project
  • Deploy to IIS web server on Windows

• Two separate targets where you will deploy the app. These could be virtual machines, web servers, on-premises physical deployment groups, or other types of deployment target. In this example, we are using Azure App Service website instances. If you decide to do the same, you will have to choose names that are unique, but it's a good idea to include "QA" in the name of one, and "Production" in the name of the other so that you can easily identify them. Use the Azure portal to create a new web app.

 

Continuous deployment (CD) triggers

 

Add stages

 

Add Pre-deployment approvals

 

Create a release

 

Monitor and track deployments

 

作者:Chuck Lu    GitHub