Merge pull request #208171 from ramiMSFT/pipelines/1973068

Rolling deployments

Author: v-dirichards

articles/virtual-machines/linux/tutorial-devops-azure-pipelines-classic.md

@@ -1,98 +1,77 @@
 ---
-title: Tutorial - Configure rolling deployments for Azure Linux virtual machines
-description: In this tutorial, you learn how to set up a continuous deployment (CD) pipeline. This pipeline incrementally updates a group of Azure Linux virtual machines using the rolling deployment strategy.
+title: Configure rolling deployments for Azure Linux virtual machines
+description: Learn how to set up a classic release pipeline and deploy your application to Linux virtual machines using the rolling deployment strategy.
 author: moala
 manager: jpconnock
 tags: azure-devops-pipelines
-
-ms.assetid: 
 ms.service: virtual-machines
 ms.collection: linux
 ms.topic: tutorial
 ms.tgt_pltfrm: azure-pipelines
 ms.workload: infrastructure
-ms.date: 4/10/2020
+ms.date: 08/15/2022
 ms.author: moala
 ms.custom: devops
-
-#Customer intent: As a developer, I want to learn about CI/CD features in Azure so that I can use Azure DevOps services like Azure Pipelines to build and deploy my applications automatically.
 ---
 
-# Tutorial - Configure the rolling deployment strategy for Azure Linux virtual machines
+# Configure the rolling deployment strategy for Azure Linux virtual machines
 
 **Applies to:** :heavy_check_mark: Linux VMs
 
-Azure DevOps is a built-in Azure service that automates each part of the DevOps process for any Azure resource. Whether your app uses virtual machines, web apps, Kubernetes, or any other resource, you can implement infrastructure as code (IaC), continuous integration, continuous testing, continuous delivery, and continuous monitoring with Azure and Azure DevOps.
-
-![The Azure portal with Azure DevOps selected under Services](media/tutorial-devops-azure-pipelines-classic/azdevops-view.png)
+Azure Pipelines provides a fully featured set of CI/CD automation tools for deployments to virtual machines. This article will show you how to set up a classic release pipeline that uses the rolling strategy to deploy your web applications to Linux virtual machines.
 
-## Infrastructure as a service (IaaS) - Configure CI/CD
+## Rolling deployments
 
-Azure Pipelines provides a fully featured set of CI/CD automation tools for deployments to virtual machines. You can configure a continuous-delivery pipeline for an Azure VM from the Azure portal.
-
-This article shows how to set up a CI/CD pipeline for rolling multimachine deployments from the Azure portal. The Azure portal also supports other strategies like [canary](./tutorial-azure-devops-canary-strategy.md) and [blue-green](./tutorial-azure-devops-blue-green-strategy.md).
+In each iteration, a rolling deployment replaces instances of an application's previous version. It replaces them with instances of the new version on a fixed set of machines (rolling set). The following walk-through shows how to configure a rolling update to virtual machines.
 
-### Configure CI/CD on virtual machines
+Using **Continuous-delivery**, you can configure rolling updates to your virtual machines within the Azure portal.
 
-You can add virtual machines as targets to a [deployment group](/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.
+1. Sign in to [Azure portal](https://portal.azure.com/) and navigate to a virtual machine.
 
-### Rolling deployments
+1. Select **Continuous delivery**, and then select **Configure**.
 
-In each iteration, a rolling deployment replaces instances of an application's previous version. It replaces them with instances of the new version on a fixed set of machines (rolling set). The following walk-through shows how to configure a rolling update to virtual machines.
+   :::image type="content" source="media/tutorial-devops-azure-pipelines-classic/azure-devops-configure.png" alt-text="A screenshot showing the continuous delivery settings.":::
 
-Using the continuous-delivery option, you can configure rolling updates to your virtual machines within the Azure portal. Here is the step-by-step walk-through:
+1. Select your **Azure DevOps Organization** and your **Project** from the dropdown menu or **Create** a new one.
 
-1. Sign in to the Azure portal and navigate to a virtual machine.
-1. In the leftmost pane of the VM settings, select **Continuous delivery**. Then select **Configure**.
+1. Select your **Deployment group** from the dropdown menu or **Create** a new one.
 
-   ![The Continuous delivery pane with the Configure button](media/tutorial-devops-azure-pipelines-classic/azure-devops-configure.png)
+1. Select your **Build pipeline**.
 
-1. In the configuration panel, select **Azure DevOps Organization** to choose an existing account or create a new one. Then select the project under which you want to configure the pipeline.  
+1. Select **Deployment strategy**, and then select **Rolling**.
 
-   ![The Continuous delivery panel](media/tutorial-devops-azure-pipelines-classic/azure-devops-rolling.png)
+    :::image type="content" source="media/tutorial-devops-azure-pipelines-classic/azure-devops-rolling.png" alt-text="A screenshot showing how to configure a rolling deployment strategy.":::
 
-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.
-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.
-1. In **Deployment strategy**, select **Rolling**.
-1. Optionally, you can tag each machine with its role. The tags "web" and "db" are examples. These tags help you target only VMs that have a specific role.
-1. Select **OK** to configure the continuous-delivery pipeline.
-1. After configuration finishes, you have a continuous-delivery pipeline configured to deploy to the virtual machine.  
+1. Optionally, you can tag each machine with its role such as *web* or *db*. These tags help you target only VMs that have a specific role.
 
-   ![The Continuous delivery panel showing Deployment history](media/tutorial-devops-azure-pipelines-classic/azure-devops-deployment-history.png)
+1. Select **OK** to configure the continuous delivery pipeline.
 
-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.
+1. After completion, your continuous delivery pipeline should look similar to the following.  
 
-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.
-1. After configuration is done, select the pipeline definition, navigate to the Azure DevOps organization, and select **Edit** for the release pipeline.
+    :::image type="content" source="media/tutorial-devops-azure-pipelines-classic/azure-devops-deployment-history.png" alt-text="A screenshot showing the continuous delivery pipeline.":::
 
-   ![Editing the rolling pipeline](media/tutorial-devops-azure-pipelines-classic/azure-devops-rolling-pipeline.png)
+1. If you want to configure multiple VMs, repeat steps 2 through 4 for the other VMs. If you use the same deployment group that already has a configured pipeline, the new VMs will just be added to the deployment group and no new pipelines will be created.
 
-1. Select **1 job, 1 task** in the **dev** stage. Select the **Deploy** phase.
+1. Select the link to navigate to your pipeline, and then select**Edit** to modify the pipeline definition.
 
-   ![Rolling pipeline tasks with the Deploy task selected](media/tutorial-devops-azure-pipelines-classic/azure-devops-rolling-pipeline-tasks.png)
+    :::image type="content" source="media/tutorial-devops-azure-pipelines-classic/azure-devops-rolling-pipeline.png" alt-text="A screenshot showing the pipeline definition.":::
 
-1. From the rightmost configuration pane, you can specify the number of machines that you want to deploy in parallel in each iteration. If you want to deploy to multiple machines at a time, you can specify the number of machines as a percentage by using the slider.  
+1. Select the tasks in the **dev** stage to navigate to the pipeline tasks, and then select **Deploy**.
 
-1. The Execute Deploy Script task by default executes the deployment script deploy.ps1 or deploy.sh. The script is in the deployscripts folder in the root folder of the published package.
+    :::image type="content" source="media/tutorial-devops-azure-pipelines-classic/azure-devops-rolling-pipeline-tasks.png" alt-text="A screenshot showing the pipeline tasks.":::
 
-   ![The Artifacts pane showing deploy.sh in the deployscripts folder](media/tutorial-deployment-strategy/package.png)
+1. You can specify the number of target machines to deploy to in parallel in each iteration. If you want to deploy to multiple machines, you can specify the number of machines as a percentage by using the slider.
 
-## Other deployment strategies
+1. The **Execute Deploy Script** task will execute the deployment script located in the root folder of the published artifacts.
 
-- [Configure the canary deployment strategy](./tutorial-azure-devops-canary-strategy.md)
-- [Configure the blue-green deployment strategy](./tutorial-azure-devops-blue-green-strategy.md)
+    :::image type="content" source="media/tutorial-deployment-strategy/package.png" alt-text="A screenshot showing the published artifacts.":::
 
-## Azure DevOps Projects
+## Resources
 
-You can get started with Azure easily. With Azure DevOps Projects, start running your application on any Azure service in just three steps by selecting:
+- [Deploy to Azure virtual machines with Azure DevOps](../../devops-project/azure-devops-project-vms.md)
+- [Deploy to Azure virtual machine scale set](/azure/devops/pipelines/apps/cd/azure/deploy-azure-scaleset.md)
 
-- An application language
-- A runtime
-- An Azure service
- 
-[Learn more](https://azure.microsoft.com/features/devops-projects/).
- 
-## Additional resources
+## Related articles
 
-- [Deploy to Azure virtual machines by using Azure DevOps Projects](../../devops-project/azure-devops-project-vms.md)
-- [Implement continuous deployment of your app to an Azure virtual machine scale set](/azure/devops/pipelines/apps/cd/azure/deploy-azure-scaleset)
+- [Configure the canary deployment strategy](./tutorial-azure-devops-canary-strategy.md)
+- [Configure the blue-green deployment strategy](./tutorial-azure-devops-blue-green-strategy.md)