![]() The pipeline will start at the DEV stage and continue to the PROD stage Setting the property value to GREEN will ensure that the next deployment will happen to the GREENĮnvironment while the BLUE environment serves all of the production traffic GREEN environment is currently catering to end-user traffic ⺠RollingDeploy/TargetEnv will be set to BLUE because the ⺠We have to set Rolling/TargetEnv property to the firstĮnvironment to which we want to deploy on the project. Of the production traffic, and the BLUE environment is ready to be In this slide we have covered pipeline for the blue green deploymentīefore running the pipeline, the GREEN environment is serving all Blue-Green, Red-Black or A/B Deployment Use Case Cont.This is an automation task to run any post certification tasks such as updating the load balancer and switching theĮnvironment in preparation for the next pipeline run (for example, update the TargetENV parameter) The system will automatically switch deployments between the BLUE and GREEN environmentsĢ CertifyDeployment This is a manual step to review and certify the deployment ![]() This is another process task similar to what is in the DEV and QA stages that the environment name is parameterized. Select the Shopping Cart application, and map the application tiers to theĬorresponding environment tiers in DEV, QA, BLUE, and GREEN ![]() Mapping the Environments to the Shopping Cart Application This slide covers how to create blue and green deployment strategy as blue green are two physically separated environments, and can be configured in the Electric Flow environment model
0 Comments
Leave a Reply. |