Skip to content

Commit feaf8e7

Browse files
author
Rami Bououni
committed
save DG
1 parent 2dbef5a commit feaf8e7

File tree

1 file changed

+25
-29
lines changed
  • docs/pipelines/release/deployment-groups

1 file changed

+25
-29
lines changed

docs/pipelines/release/deployment-groups/index.md

Lines changed: 25 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Use deployment groups in Classic release pipelines
3-
description: Learn how to create and use deployment groups, which are logical groups of target machines for Classic release pipelines in Azure Pipelines.
3+
description: Learn how to create and use deployment groups in Classic release pipelines in Azure Pipelines.
44
ms.assetid: 21416B0A-F60F-436F-AB46-D6C2A54D5707
55
ms.topic: how-to
66
ms.author: ronai
77
author: RoopeshNair
8-
ms.date: 08/27/2024
8+
ms.date: 05/22/2025
99
monikerRange: '<= azure-devops'
1010
"recommendations": "true"
1111
---
@@ -14,68 +14,64 @@ monikerRange: '<= azure-devops'
1414

1515
[!INCLUDE [version-lt-eq-azure-devops](../../../includes/version-lt-eq-azure-devops.md)]
1616

17-
Similar to an [agent pool](../../agents/pools-queues.md), a deployment group is a logical set of target machines that each have a deployment agent installed. Deployment groups can represent environments such as "Development," "Test," or "Production." Every physical or virtual machine (VM) in the deployment group interacts with Azure Pipelines to coordinate the deployment tasks. Deployment groups are different from [deployment jobs](../../process/deployment-jobs.md), which are collections of task-related steps defined in YAML pipelines.
17+
Similar to an [agent pool](../../agents/pools-queues.md), a deployment group is a logical set of target machines, each have a deployment agent installed. Deployment groups typically represent environments such as *Development, *Test*, or *Production*. Each physical or virtual machine in the deployment group communicates with Azure Pipelines to coordinate deployment tasks. Deployment groups differ from [deployment jobs](../../process/deployment-jobs.md), which are collections of task-related steps defined in YAML pipelines.
1818

19-
>[!NOTE]
20-
>Deployment groups are available only for Classic release pipelines.
19+
Deployment groups give you a flexible way to manage and monitor your deployment targets. You can define the security context and runtime environment for agents, assign roles and permissions to team members, and get real-time visibility into deployments with live logs for each server. You can also use tags to target specific machines, making deployments more precise and efficient.
2120

22-
By using deployment groups, you can:
23-
24-
- Specify the security context and runtime targets for agents.
25-
- Add users and give them appropriate permissions to administer, manage, view, and use the group.
26-
- View live logs for each server while a deployment happens, and download logs to track deployments for individual servers.
27-
- Use tags to limit deployments to specific sets of target servers.
21+
> [!NOTE]
22+
> Deployment groups are only available in Classic release pipelines.
2823
2924
## Prerequisites
3025

31-
- An Azure DevOps organization and project. To create an organization and project, see [Create a new organization](../../../organizations/accounts/create-organization.md) or [Create a project in Azure DevOps](../../../organizations/projects/create-project.md).
32-
- Administrative access to at least one Windows or Linux physical or virtual machine to use as a deployment target.
26+
| **Product** | **Requirements** |
27+
|--------------------|--------------------|
28+
| **Azure DevOps** | - An Azure DevOps [organization](../../../organizations/accounts/create-organization.md).<br>- An Azure DevOps [project](../../../organizations/projects/create-project.md).<br> - Administrator permissions on a Windows or Linux machine to install and configure the deployment agent. |
3329

3430
## Create a deployment group
3531

36-
1. From your Azure DevOps project, select **Pipelines** > **Deployment groups**.
37-
38-
:::image type="content" source="media/pipelines-deployment-groups.png" alt-text="A screenshot showing Deployment groups in the Pipelines menu.":::
32+
1. Sign in to your Azure DevOps organization, and navigate to your project.
3933

40-
1. On the **Deployment groups** screen, select **New**, or select **Add a deployment group** if this deployment group is the first one in the project.
34+
1. In your project, select **Pipelines**, then select **Deployment groups**.
4135

42-
:::image type="content" source="media/add-deployment-groups.png" alt-text="A screenshot showing Add a deployment group.":::
36+
1. On the **Deployment groups** page, select **New**. If this is your first deployment group, select **Add a deployment group**.
4337

4438
1. Enter a **Deployment group name** and then select **Create**.
4539

4640
1. On the next screen, select **Windows** or **Linux** for the **Type of target to register**. A registration script is generated.
4741

48-
1. Select **Use a personal access token in the script for authentication**, and then select **Copy script to the clipboard**.
42+
1. Select **Use a personal access token in the script for authentication**, then select **Copy script to the clipboard**.
4943

5044
1. Save the copied script to run on all the target machines in your deployment group.
5145

52-
:::image type="content" source="media/generated-script.png" alt-text="A screenshot showing the generated registration script and other settings.":::
46+
:::image type="content" source="media/generated-script.png" alt-text="A screenshot displaying how to create a deployment group in Azure Pipelines.":::
5347

5448
## Register target servers
5549

5650
To register each target server in the deployment group:
5751

58-
1. Sign in to the machine with an administrative account and run the copied script. For Windows machines, use an elevated PowerShell command prompt.
52+
1. Sign in to the machine using an account with administrator permissions, and run the copied script. For Windows machines, use an elevated PowerShell command prompt.
5953

6054
:::image type="content" source="media/register-servers.png" alt-text="A screenshot that shows registering deployment groups servers.":::
6155

62-
1. To assign tags that let you limit deployments to certain servers in a [deployment group job](../../process/deployment-group-phases.md), enter *Y* when prompted to enter tags, and then enter a tag or tags.
56+
1. When prompted to add tags (can be used to target deployments to specific servers in a [deployment group job](../../process/deployment-group-phases.md)), enter Y, then provide one or more tags. Tags are case insensitive, limited to 256 characters each, and there's no limit to the number of tags you can use.
6357

64-
Tags are limited to 256 characters each, are case insensitive, and there's no limit to the number of tags you can use.
58+
1. Once setup is complete, the script should return the following message:
6559

66-
After you set up a target server, the script should return the message `Service vstsagent.{organization-name}.{computer-name} started successfully`.
60+
```
61+
Service vstsagent.{organization-name}.{computer-name} started successfully.
62+
```
6763
6864
## Install and upgrade agents
6965
70-
Every target server in the deployment group requires a deployment agent. The generated registration script for target servers installs an agent. Alternatively, you can use the following methods to install agents:
66+
Every target server in the deployment group requires a deployment agent. The generated registration script for target servers installs an agent. Alternatively, you can install agents using one of the following methods:
7167
72-
- If the target servers are Azure VMs, you can easily set up your servers by [installing the Azure Pipelines agent extension](./howto-provision-deployment-group-agents.md#install-the-azure-pipelines-agent-azure-vm-extension) on each VM.
68+
- For Azure VMs, you can easily set up your servers by [installing the Azure Pipelines agent extension](./howto-provision-deployment-group-agents.md#install-the-azure-pipelines-agent-azure-vm-extension) on each VM.
7369
74-
- You can use the [AzureResourceGroupDeploymentV2 task](./howto-provision-deployment-group-agents.md#use-the-azureresourcegroupdeploymentv2-task) in your release pipeline to create and register a deployment group dynamically.
70+
- Use the [AzureResourceGroupDeploymentV2 task](./howto-provision-deployment-group-agents.md#use-the-azureresourcegroupdeploymentv2-task) in a release pipeline to dynamically create and register deployment group agents.
7571
76-
For more information about these methods, see [Provision agents for deployment groups](howto-provision-deployment-group-agents.md).
72+
See [Provision agents for deployment groups](howto-provision-deployment-group-agents.md) for more details.
7773
78-
To upgrade the agents on target servers to the latest version without having to redeploy them, select the **More actions** ellipsis next to the deployment group on the **Deployment groups** page and select **Update targets**. For more information, see [Azure Pipelines agents](../../agents/agents.md).
74+
To upgrade deployment agents to the latest version without redeploying, go to the **Deployment groups** page, select the **More actions** ellipsis next to your deployment group, and choose **Update targets**. See [Agents](../../agents/agents.md) for more details.
7975
8076
:::image type="content" source="media/update-targets-deployment-groups.png" alt-text="A screenshot showing how to update targets in deployment groups.":::
8177

0 commit comments

Comments
 (0)