You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/tutorial-azure-devops-blue-green-strategy.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ This article shows how to set up a CI/CD pipeline that uses the blue-green strat
27
27
28
28
### Configure CI/CD on virtual machines
29
29
30
-
You can add virtual machines as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups). You can then target them for multimachine updates. After you deploy to machines, view **Deployment History** within a deployment group. This view lets you trace from VM to the pipeline and then to the commitment.
30
+
You can add virtual machines as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups). You can then target them for multimachine updates. After you deploy to machines, view **Deployment History** within a deployment group. This view lets you trace from VM to the pipeline and then to the commit.
31
31
32
32
### Blue-green deployments
33
33
@@ -49,19 +49,19 @@ Using the continuous-delivery option, you can configure blue-green deployments t
49
49
1. A deployment group is a logical set of deployment target machines that represent the physical environments. Dev, Test, UAT, and Production are examples. You can create a new deployment group or select an existing one.
50
50
1. Select the build pipeline that publishes the package to be deployed to the virtual machine. The published package should have a deployment script named deploy.ps1 or deploy.sh in the deployscripts folder in the package's root folder. The pipeline runs this deployment script.
51
51
1. In **Deployment strategy**, select **Blue-Green**.
52
-
1. Add a "blue" or "green" tag to VMs that are to be part of blue-green deployments. If a VM is for a standby role, tag it as "green." Otherwise, tag it as "blue."
52
+
1. Add a "blue" or "green" tag to VMs that are to be part of blue-green deployments. If a VM is for a standby role, tag it as "green". Otherwise, tag it as "blue".
53
53
54
54
55
55
56
56
1. Select **OK** to configure the continuous-delivery pipeline to deploy to the virtual machine.
1.Select **Edit**for the release pipeline in Azure DevOps Pipelines to see the pipeline configuration. The pipeline has these three phases:
60
+
1.The deployment details for the virtual machine are displayed. You can select the link to go to the release pipeline in Azure DevOps. In the release pipeline, select **Edit**to view the pipeline configuration. The pipeline has these three phases:
61
61
62
-
1. This phase is a deployment-group phase. Applications are deployed to standby VMs, which are tagged as "green."
63
-
1.The pipeline pauses and waits for manual intervention to resume the run.
64
-
1.After deployment is stable, users can redirect traffic to "green" VMs and resume the pipeline run. That run swaps the "blue" and "green" tags in the VMs. This technique ensures that VMs with older application versions are tagged as "green." During the next pipeline run, applications are deployed to these VMs.
62
+
1. This phase is a deployment-group phase. Applications are deployed to standby VMs, which are tagged as "green".
63
+
1.In this phase, the pipeline pauses and waits for manual intervention to resume the run. Users can resume the pipeline run once they have manually ensured stability of deployment to VMs tagged as "green".
64
+
1.This phase swaps the "blue" and "green" tags in the VMs. This ensures that VMs with older application versions are now tagged as "green". During the next pipeline run, applications will be deployed to these VMs.
65
65
66
66
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/tutorial-azure-devops-canary-strategy.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ This article shows how to set up a CI/CD pipeline that uses the canary strategy
27
27
28
28
### Configure CI/CD on virtual machines
29
29
30
-
You can add virtual machines as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups). You can then target them for multimachine updates. After you deploy to machines, view **Deployment History** within a deployment group. This view lets you trace from VM to the pipeline and then to the commitment.
30
+
You can add virtual machines as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups). You can then target them for multimachine updates. After you deploy to machines, view **Deployment History** within a deployment group. This view lets you trace from VM to the pipeline and then to the commit.
31
31
32
32
### Canary deployments
33
33
@@ -53,17 +53,17 @@ Using the continuous-delivery option, you can configure canary deployments to yo
53
53
54
54
1. Select **OK** to configure the continuous-delivery pipeline to deploy to the virtual machine.
1.Select **Edit**for the release pipeline in Azure DevOps Pipelines to see the pipeline configuration. The pipeline has these three phases:
58
+
1.The deployment details for the virtual machine are displayed. You can select the link to go to the release pipeline in Azure DevOps. In the release pipeline, select **Edit**to view the pipeline configuration. The pipeline has these three phases:
59
59
60
-
1. This phase is a deployment-group phase. Applications are deployed to VMs that are tagged as "canary."
61
-
1.The pipeline pauses and waits for manual intervention to resume the run.
62
-
1.After deployment is stable, users can resume the pipeline run that deploys to VMs tagged as "prod."
60
+
1. This phase is a deployment-group phase. Applications are deployed to VMs that are tagged as "canary".
61
+
1.In this phase, the pipeline pauses and waits for manual intervention to resume the run.
62
+
1.This is again a deployment group phase. The update is now deployed to VMs tagged as "prod".
63
63
64
64
65
65
66
-
1. Before resuming the pipeline run, ensure that at least one VM is tagged as "prod." In the third phase of the pipeline, applications are deployed to only those VMs that have the "prod" tag.
66
+
1. Before resuming the pipeline run, ensure that at least one VM is tagged as "prod". In the third phase of the pipeline, applications are deployed to only those VMs that have the "prod" tag.
67
67
68
68
1. The Execute Deploy Script task by default runs the deployment script deploy.ps1 or deploy.sh. The script is in the deployscripts folder in the root folder of the published package. Ensure that the selected build pipeline publishes the deployment in the root folder of the package.
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/tutorial-devops-azure-pipelines-classic.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ This article shows how to set up a CI/CD pipeline for rolling multimachine deplo
31
31
32
32
### Configure CI/CD on virtual machines
33
33
34
-
You can add virtual machines as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups). You can then target them for multimachine updates. After you deploy to machines, view **Deployment History** within a deployment group. This view lets you trace from VM to the pipeline and then to the commitment.
34
+
You can add virtual machines as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups). You can then target them for multimachine updates. After you deploy to machines, view **Deployment History** within a deployment group. This view lets you trace from VM to the pipeline and then to the commit.
35
35
36
36
### Rolling deployments
37
37
@@ -57,7 +57,8 @@ Using the continuous-delivery option, you can configure rolling updates to your
1. The deployment to the virtual machine is in progress. You can select the link to go to the pipeline. Select **Release-1** to view the deployment. Or select **Edit** to modify the release-pipeline definition.
60
+
1. The deployment details for the virtual machine are displayed. You can select the link to go to the pipeline, **Release-1** to view the deployment, or **Edit** to modify the release-pipeline definition.
61
+
61
62
1. If you're configuring multiple VMs, repeat steps 2 through 4 for other VMs to add to the deployment group. If you select a deployment group that already has a pipeline run, the VMs are just added to the deployment group. No new pipelines are created.
62
63
1. After configuration is done, select the pipeline definition, navigate to the Azure DevOps organization, and select **Edit** for the release pipeline.
0 commit comments