Release Pipeline - Unlocked Package Based Deployment

Deploy Stage

Release pipelines are one of the most exciting benefits of using Azure Pipelines, which is not just for Continuous Integration but can also act us an automated release orchestrator. This sample pipeline demonstrates how to orchestrate an installation of an unlocked package across various environments.

This pipeline can be triggered manually by some one releasing a previously build artifact to the the environment or automated. This could be automated using the various mechanisms available in Azure Pipelines

Pipeline Snapshot

Release Pipeline
Tasks in a stage
Release Pipeline

Tasks in a stage
Minimal Tasks in a stage of unlocked package deployment

Tasks Snapshot in one of the stages

The steps that are part of the pipeline in an individual stage are

  1. Authenticate an Org ( In this case, it is authenticating against DevHub)

  2. Authenticate an Org ( In this case, it is authenticating against the Sandbox to be deployed)

Please note, we still recommend at this stage to use classic pipelines for Continuous Delivery. YAML Pipelines are missing some elements like Manual Intervention which are essential for modelling Salesforce Deployment

Edit on GitHub