-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Open
Description
Task name
AzureResourceManagerTemplateDeployment
Task version
3.262.0
Environment type (Please select at least one enviroment where you face this issue)
- Self-Hosted
- Microsoft Hosted
- VMSS Pool
- Container
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Version Azure DevOps Server 2022.1 (AzureDevOpsServer_20231109.2)
Operation system
Windows Server 2025
Question
Hi,
In our company we frequently use this task to deploy a bicep and bicepparam towards our Azure Cloud environment(s). Now I was digging through and following the code where eventually the following code caught my eye:
https://github.com/microsoft/azure-pipelines-tasks-common-packages/blob/626b27c67dcbc98a222c3ed13d47903107e8f44a/common-npm-packages/azure-arm-rest/AzureServiceClientBase.ts#L174
For example we have a small bicep running via this task only doing some existing(/reference) since we want to know hostnames. That one takes on its own in the Deployments-tab not even 1 second, but in my Azure DevOps Server (on-premise) Pipeline about 40 seconds and thus significantly (relatively) slowing down stuff. Even on larger biceps which really does stuff, we also see way longer running tasks in ADO compared to the Deployments-tab in Azure.
Is there any reason for such a big wait, could it be lower or could we even by start/first rely on the retry-after? Although mostly I see the 15-second.
The reason I am using this task is that we have seen it in ymls presented by ADO when creating one based on a dotnet api, we are a software development company, in a repo. If there are perhaps better/other/different ways I am open to it.
~ xhoogland
Note: This is a cross-post with https://github.com/microsoft/azure-pipelines-tasks-common-packages/issues/504