Azure DevOps REST API添加持续部署触发器PATCH请求报错求助

尝试为现有发布触发器添加新分支，使用GET请求可正常获取发布定义内容，但执行PATCH更新操作时失败，报错信息如下：

"innerException": null,   
"message": "VS403051: Could not delete pipeline with ID 515 because it was not found. Specify a valid ID and try again.",   
"typeName": "Microsoft.VisualStudio.Services.ReleaseManagement.Data.Exceptions.DeletedReleaseDefinitionNotFoundException"

原参考代码：

$releaseDefinitionId = "515"
$pat = "test_pat_token"

# Define the continuous deployment trigger
$continuousDeploymentTrigger = @{
    triggerType = "continuousIntegration"
    settingsSourceType = "definition"
    branchFilters = @(
        "+refs/heads/develop"
    )
}

# Convert the continuous deployment trigger to JSON format
$body = @{
    triggers = @(
        $continuousDeploymentTrigger
    )
} | ConvertTo-Json

# Define the REST API URL
$url = "https://vsrm.dev.azure.com/org/project/_apis/release/definitions/$($releaseDefinitionId)?api-version=7.1-preview.4"

# Invoke the REST API to update the release definition
Invoke-RestMethod -Uri $url -Method Patch -Headers @{
    Authorization = "Basic " + [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(":$($pat)"))
} -Body $body -ContentType "application/json"

问题分析 #

原代码的核心问题是直接用新的triggers数组覆盖了原有触发器集合，这会删除所有已存在的触发器，进而触发关联管道找不到的错误。Azure DevOps的PATCH请求需要基于现有资源进行增量修改，而非完全覆盖集合。

优化后的代码 #

正确的流程是先获取当前发布定义的完整内容，找到目标CI触发器后，在其分支列表中添加新分支，再提交更新：

$releaseDefinitionId = "515"
$pat = "test_pat_token"
$orgName = "org"
$projectName = "project"
$newBranch = "+refs/heads/develop"

# 构建API请求头
$headers = @{
    Authorization = "Basic " + [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(":$($pat)"))
}

# 1. 获取当前发布定义的完整内容
$url = "https://vsrm.dev.azure.com/$orgName/$projectName/_apis/release/definitions/$releaseDefinitionId?api-version=7.1-preview.4"
$currentDefinition = Invoke-RestMethod -Uri $url -Method Get -Headers $headers -ContentType "application/json"

# 2. 找到类型为continuousIntegration的触发器
$ciTrigger = $currentDefinition.triggers | Where-Object { $_.triggerType -eq "continuousIntegration" }

if ($ciTrigger) {
    # 3. 检查分支是否已存在，避免重复添加
    if ($ciTrigger.branchFilters -notcontains $newBranch) {
        $ciTrigger.branchFilters += $newBranch
    }
} else {
    # 如果没有CI触发器，创建新的触发器
    $ciTrigger = @{
        triggerType = "continuousIntegration"
        settingsSourceType = "definition"
        branchFilters = @($newBranch)
    }
    $currentDefinition.triggers += $ciTrigger
}

# 4. 准备PATCH请求的body，只传递修改后的triggers
$body = @{
    triggers = $currentDefinition.triggers
} | ConvertTo-Json -Depth 10

# 5. 执行PATCH更新
Invoke-RestMethod -Uri $url -Method Patch -Headers $headers -Body $body -ContentType "application/json"

关键优化点 #

• 先获取现有定义，确保基于当前状态修改，避免覆盖原有触发器
• 检查分支是否已存在，防止重复添加
• 使用-Depth 10确保复杂JSON结构被正确序列化
• 保留原有触发器的所有配置，仅更新分支列表

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