I ve also seen that some people says that it could be a pipelines delay bug from Azure DevOps, and some of this people get solved this bug by itself after some hours/days, but I need to solve it urgent.
是的,可以在数小时/日之后收回。 但是,如果现在继续存在,请尝试以下选择:
purchase another parallel job, after it works(pipeline can grant the agent), delete the job purchased(link here).
如果做不到一定的工作,则使用来授予集合地位:
回复的<编码>规定国家代码>即为<代码> 如果该编码not
,则通过PowerShell script(向贵方出售 pool和 agent):
Param(
[string]$organization = "yourorgname",
[string]$token = "PAT"
)
$base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $user,$token)))
$url="https://dev.azure.com/$organization/_apis/distributedtask/pools/9/agents/8?api-version=5.1"
$body = @"
{
"Id": 8,
"ProvisioningState": "Deallocated"
}
"@
Invoke-RestMethod -Uri $url -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)} -Body $body -ContentType "application/json" -Method PATCH
如果问题持续存在,也可由<代码>造成。 紧急集合服务(9)代码> 身份从<条码>中删除。 请注意,这里的身份号码(9)可能与贵组织不同。 请查看link。
www.un.org/Depts/DGACM/index_spanish.htm 如果你需要紧急解决,第一种办法是通过“门户”提出支持请求。 https://azure.microsoft.com/en-us/support/plans/“rel=“nofollow noreferer” 与您的订阅相关的支持计划? Click ,以提出支持请求。 请分享铺设管道,并在支助请求说明中公布细节。