删除Azure容器应用耗时过长致Azure DevOps管道超时的解决方案咨询

Fire-and-Forget Asynchronous Deletion #

You can trigger resource group deletion without waiting for completion using Azure CLI or PowerShell's asynchronous flags:

• Azure CLI: Use the --no-wait parameter to kick off deletion in the background:

  az group delete --name <resource-group-name> --yes --no-wait
  

• PowerShell: Use the -AsJob parameter to run deletion as a background job:

  Remove-AzResourceGroup -Name <resource-group-name> -Force -AsJob
  

This lets your pipeline exit immediately after triggering deletion. Note that you won’t get real-time success/failure feedback—you’ll need to check Azure Portal logs or add a separate verification step later if confirmation is required.

Parallelize Deletion of Multiple Resource Groups #

Instead of deleting resource groups sequentially, run their deletion in parallel using Azure DevOps pipeline matrix strategies. This cuts total runtime from 1+ hours (for 3 RGs) to ~25 minutes:

jobs:
- job: DeleteResourceGroups
  strategy:
    matrix:
      RG1:
        RG_NAME: 'rg-container-apps-1'
      RG2:
        RG_NAME: 'rg-container-apps-2'
      RG3:
        RG_NAME: 'rg-container-apps-3'
  steps:
  - script: az group delete --name $(RG_NAME) --yes --no-wait
    displayName: 'Delete Resource Group $(RG_NAME)'

Each resource group deletion runs in its own parallel job, so all process simultaneously.

Optimize Deletion Order for Container App Environments #

Container App Environments can take time to delete due to underlying dependencies. Speed up the process by deleting container apps first before the resource group:

# Delete all container apps in the RG first
az containerapp list --resource-group <rg-name> --query "[].name" -o tsv | xargs -I {} az containerapp delete --name {} --resource-group <rg-name> --yes --no-wait

# Then delete the resource group
az group delete --name <rg-name> --yes --no-wait

Removing dependent resources upfront reduces load on the RG deletion process, shaving minutes from each deletion.

Use Azure Automation Runbooks for Deletion #

Offload deletion to an Azure Automation runbook. Your pipeline only needs to trigger the runbook, then exit immediately:

1. Create an Azure Automation account and a runbook with deletion logic (e.g., PowerShell to delete RGs asynchronously).
2. Add a pipeline step to start the runbook:

   az automation runbook start --name "DeleteResourceGroups" --resource-group <automation-rg-name> --automation-account-name <automation-account-name>
   

The runbook runs independently in Azure, avoiding pipeline timeouts entirely. Configure runbook logging to track deletion status later.

Addressing Pipeline Timeouts #

Even with timeoutInMinutes: 0, Microsoft-hosted agents have default runtime limits (60 minutes for free tiers, up to 360 minutes for paid). Using asynchronous or parallel methods ensures your pipeline finishes before hitting these limits.

内容的提问来源于stack exchange，提问作者Maytham Fahmi