Multistage Pipeline with Deployment Slots in Azure DevOps

preview_player
Показать описание
Create Multistage Pipeline with Deployment Slots in Azure DevOps
1. Create multiple deployment slots in Azure
2. Create build pipelines for QA, UAT, and Prod
3. Create multiple stages in the release pipeline

#Azure #AzureDevOps #InGeniusYT #AzureTalk #Multistage
Рекомендации по теме
Комментарии
Автор

CI-CD is fast deployment-environment to environment using mostly automated testing. We use 1 pipeline in which Dev stage is connected to QA which is connected to UAT which is connected to Prod. At each stage we can have approvers and sign offs before proceeding to the next stage. The solution you have is Not what CI/CD promotes since you have separate pipelines for each environment.

fav
Автор

gr8 Question, I tried the same process, but change in any branch like QA or UAT, all stages are triggered in release pipeline instead of that stage, am I missing something ?
Do we need to add any artifact triggers ?

ssdk
Автор

So if I want to create a multibranch pipeline I'd have to do it manually? I think we should be able to have dropdowns to select env, branch and others so we don't maintain the same code multiple times. Anyway thanks for this way of solving it

rodrigocaballerohurtado
Автор

One confusion, you have 3 branches for different environments? Why is that so? Single branch code should be flowing to 3 different web apps based on stages passed.
So, there should be a single branch to trigger on and single pipeline with 3 stages configured to 3 web apps either automatically or with human approval.
Is there anything I missed?

microtech
Автор

Thanks for the informative video.
I created the QA slot, release is also successful but end point URL is giving below error "The specified CGI application encountered an error and the server terminated the process."

Any idea how to correct this, I am using java maven builds

cloudyaffair
Автор

Thanks for the great vedio. I need to know about the configuration like in react my configuration picks from the .env file and we will manage based on different pipeline on this.

techbiz
Автор

at 14:00 you show all stages in the pipeline but that is not how I saw you configure it earlier...

seanwauchope
Автор

How to setup single bulid pipeline with multiple release environment

bytesmintue
Автор

hello, cant we just have environment variables instead of creating pipelines for each environment? thanks

sid
Автор

how to deploy multiple azure functions in one pipeline

SouravSingh-mnut
Автор

Nice video i have a quick question if supposed insted of slots we are using different webapp for different environment then.... It's is not good Or Bill will be more??

GyaniBacha
Автор

Good video, But I have one query here.
In my case I have enabled continous trigger for multiple branches in same build pipeline and enabled deployment trigger for release pipeline and pointing to respective app server slots. But my point here is how can I differentiate like if tigger happens in dev branch only deploy to dev slot? Because if we commit on any included beanch this build pipeline will trigger and published an artifact with generic name. So how can I differentiate this? Please help me with this

Thanks in Advance

sainadhpotta
Автор

Simply superb ... well explained.. what is the way to contact you..

Mr