📓
AzureDevOps-CI/CD
  • Preface
  • Prerequisites
  • Create an Project
  • Create Personal Access Token
  • Create Repository
  • Cloning the Azure Repository
  • Saving changes with commit and push
  • Updating Code with fetch and pull
  • Pushing an existing repository from the command line
  • Working with GitHub
  • Create Pipeline for ADO
  • Create Release Pipeline for ADO
  • Conclusion
Powered by GitBook
On this page

Was this helpful?

Create Release Pipeline for ADO

PreviousCreate Pipeline for ADONextConclusion

Last updated 5 years ago

Was this helpful?

An artifact is a deployable component of your application. It is typically produced through a Continuous Integration or a build pipeline. Azure Pipelines releases can deploy artifacts that are produced by a wide range of artifact sources such as Azure Pipelines build, Jenkins, or Team City.

You define the release pipeline using stages, and restrict deployments into or out of a stage using . You define the automation in each stage using jobs and tasks. You use to generalize your automation and to control when the deployments should be kicked off automatically.

An example of a release pipeline that can be modeled through a release pipeline in shown below:

Artifacts in a pipeline and release

In this example, a release of a website is created by collecting specific versions of two builds (artifacts), each from a different build pipeline. The release is first deployed to a Dev stage and then forked to two QA stages in parallel. If the deployment succeeds in both the QA stages, the release is deployed to Prod ring 1 and then to Prod ring 2. Each production ring represents multiple instances of the same website deployed at various locations around the globe.

approvals
variables
triggers