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.
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.
gr8 tutorial.....Quick 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 ?
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?
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
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
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??
Having individual web apps is not cost effective as of creating slots. Also, it depends on your app service plan that how many web app you can create and for how long the web app would be active per day. Please read out the Microsoft official documentation for App Service Plan for more detail.
Thanks for writing in. Creating the environment variable would help you to get the dynamic values but practically you have to create separate pipelines for different-different environments. I would further look into it if there is any such option possible.
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
Sorry for the late reply. I was away for some reason. I think you must go through the concept of multi stage cd pipeline. This would definitely give you good insight. Please read out the following official documentation. docs.microsoft.com/en-us/azure/devops/pipelines/release/define-multistage-release-process?view=azure-devops
