Skip to content

Commit 3beb5a2

Browse files
raiyanalamjuliakm
andauthored
Update articles/virtual-machines/linux/tutorial-azure-devops-canary-deployment-strategy.md
Co-Authored-By: Julia Kulla-Mader <[email protected]>
1 parent f95e997 commit 3beb5a2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-machines/linux/tutorial-azure-devops-canary-deployment-strategy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Azure Pipelines provides a complete, fully featured set of CI/CD automation tool
2626

2727
**Configure CI/CD on Virtual Machines**
2828

29-
Virtual machines can be added as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups) and can be targeted for multi-machine updates. Once deployed, Deployment History views within Deployment Group provides traceability from VM to the pipeline and then to the commit.
29+
Virtual machines can be added as targets to a [deployment group](https://docs.microsoft.com/azure/devops/pipelines/release/deployment-groups) and can be targeted for multi-machine updates. Once deployed, the **Deployment History** within your deployment group provides traceability from VM to the pipeline and then to the commit.
3030

3131

3232
**Canary Deployments**: A canary deployment reduces risk by slowly rolling out the change to a small subset of users. As you gain more confidence in the new version, you can start releasing it to more servers in your infrastructure and routing more users to it.

0 commit comments

Comments
 (0)