0

I'm new to tge release pipeline concept in Azure DevOps, we have four environments(Dev,QA,UAT,Prod) and the idea is once code changes are done then we need to trigger the dev stage manually and once it successfully runs then the code will automatically need to trigger other higher environments through approval, How do I need to design this through release pipelines.

As well I m having 5 build pipeline can I trigger these 5 build in single release pipeline

Please give idea to do the task

Thanks in advance

DreadedFrost
  • 2,602
  • 1
  • 11
  • 29
vithya m
  • 11
  • 4
  • Modern approach is to use your CI (ADO) to build and then pull releases from environments - see my tutorial here for a possible way to do it (uses our tool) - https://worklifenotes.com/2023/05/12/how-to-promote-software-to-production-with-reliza-hub/ – taleodor Jun 19 '23 at 13:13
  • Can you elaborate if you are leveraging YAML pipelines or classic releases? For more information refer to this [stack overflow post](https://stackoverflow.com/questions/76368866/azure-pipelines-releases-versus-environment-for-release-management-and-deployme/76369529#76369529) – DreadedFrost Jun 19 '23 at 15:01
  • @DreadedFrost At yaml pipelines – vithya m Jun 20 '23 at 11:23

1 Answers1

0

To achieve this will need to leverage Azure DevOps Environments which are:

An environment is a collection of resources that you can target with deployments from a pipeline. Typical examples of environment names are Dev, Test, QA, Staging, and Production. An Azure DevOps environment represents a logical target where your pipeline deploys software.

The environment is configured at the job level and each environment can have a separate set of gates or approvals.

Based upon your scenario I would recommend one pipeline with 6 stages. Build->Dev->QA->UAT-PROD. Each stage should ideally be a YAML template so you'd write the steps once and pass in parameters/variables to the stage. However if starting writing out all the tasks/jobs is okay. It just will be a lot of copy and pasting.

Here is a blog series on YAML pipelines to get you started.

DreadedFrost
  • 2,602
  • 1
  • 11
  • 29
  • Thanks for your input, I am having templates ready but I need to deploy this via release pipeline, how I need to achieve deployment via release pipeline with 4 stages(Dev-->QA-->UAT-->PROD) – vithya m Jun 21 '23 at 07:33
  • You said you were doing YAMLPipelines. YAML Pipelines are not [Classic Release Pipelines](https://learn.microsoft.com/en-us/azure/devops/pipelines/release/define-multistage-release-process?view=azure-devops) they are different. – DreadedFrost Jun 21 '23 at 11:14
  • As of now we are using YAML pipelines now planning to change to classic release pipelines which is new for me, please give me idea on release pipeline for 4 stages – vithya m Jun 21 '23 at 15:52
  • Would strongly advise not to go from YAML to Classic. Here's a [post summarizing why](https://stackoverflow.com/questions/76368866/azure-pipelines-releases-versus-environment-for-release-management-and-deployme/76369529#76369529). – DreadedFrost Jun 21 '23 at 16:11
  • Really thanks for this useful information, as per client ask we thought of doing it but for sure we will let them know this point, thanks a lot. – vithya m Jun 22 '23 at 17:11