使用ASP.NET Yaml模板的新Azure DevOps管道失败 [英] New Azure DevOps pipeline using ASP.NET yaml template failing

问题描述

我有一个带有.NET Core 3.0网站解决方案的GitHub存储库.在Azure DevOps中，我通过向导在向导的配置"步骤上使用 ASP.NET Core 模板创建了一个链接到该存储库的新管道.这是我的YAML外观:

I have a GitHub repository with a .NET Core 3.0 website solution in it. In Azure DevOps, I went through the wizard to create a new pipeline linked to that repository using the ASP.NET Core template on the Configure step of the wizard. This is what my YAML looks like:

# ASP.NET Core
# Build and test ASP.NET Core projects targeting .NET Core.
# Add steps that run tests, create a NuGet package, deploy, and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/dotnet-core

trigger:
- develop

pool:
  vmImage: 'ubuntu-latest'

variables:
  buildConfiguration: 'Release'

steps:
- script: dotnet build --configuration $(buildConfiguration)
  displayName: 'dotnet build $(buildConfiguration)'

当我尝试手动运行管道进行测试时，这是我每次都得到的输出:

When I try to manually run the pipeline to test it, this is the output I get everytime:

##[warning]There was a failure in sending the provision message: Unexpected response code from remote provider NotFound
,##[warning]There was a failure in sending the provision message: Unexpected response code from remote provider NotFound
,##[warning]There was a failure in sending the provision message: Unexpected response code from remote provider NotFound
,##[warning]There was a failure in sending the provision message: Unexpected response code from remote provider NotFound
,##[warning]There was a failure in sending the provision message: Unexpected response code from remote provider NotFound
,##[error]Provisioning request delayed or failed to send 5 time(s). This is over the limit of 3 time(s).
Pool: Azure Pipelines
Image: ubuntu-latest
Started: Yesterday at 10:04 PM
Duration: 10h 54m 5s

Job preparation parameters
ContinueOnError: False
TimeoutInMinutes: 60
CancelTimeoutInMinutes: 5
Expand:
  MaxConcurrency: 0
  ########## System Pipeline Decorator(s) ##########

  Begin evaluating template 'system-pre-steps.yml'
Evaluating: eq('true', variables['system.debugContext'])
Expanded: eq('true', Null)
Result: False
Evaluating: resources['repositories']['self']
Expanded: Object
Result: True
Evaluating: not(containsValue(job['steps']['*']['task']['id'], '6d15af64-176c-496d-b583-fd2ae21d4df4'))
Expanded: not(containsValue(Object, '6d15af64-176c-496d-b583-fd2ae21d4df4'))
Result: True
Evaluating: resources['repositories']['self']['checkoutOptions']
Result: Object
Finished evaluating template 'system-pre-steps.yml'
********************************************************************************
Template and static variable resolution complete. Final runtime YAML document:
steps:
- task: 6d15af64-176c-496d-b583-fd2ae21d4df4@1
  inputs:
    repository: self

我认为也许 ubuntu-latest 不再是有效的vmImage，所以我尝试将其更改为 ubuntu-18.04 并获得了相同的结果.由Micosoft托管的代理文档说任何一个都应该有效.

I thought maybe ubuntu-latest was maybe no longer a valid vmImage, so I tried changing it to ubuntu-18.04 and got the same result. The Micosoft-hosted agents documentation says either should be valid.

我的Yaml文件有问题吗?我以前使用过旧的no-yaml界面就没有问题，因此已经建立了设置管道，所以我有些困惑.

Do I have something wrong with my yaml file? I have setup pipelines before with the old no-yaml interface with no issues, so I am a little confused.

推荐答案

我正在浏览我的帐户，发现我的代理池"设置对该项目有些怀疑.它显示了我有11个可用的在线代理，即使我在私有存储库上使用免费计划也是如此，因此它应该只有一个.

I was looking through my account and noticed my Agent Pool settings looked a little suspect on the project. It showed I had 11 available agents that were online even though I was using the free plan on a private repository so it should only have one.

我最终删除了我的Azure DevOps组织并创建了一个新组织.现在，我最初发布的YAML配置可以正常工作.

I ended up deleting my Azure DevOps organization and creating a new one. Now the YAML configuration I initially posted works fine.

这篇关于使用ASP.NET Yaml模板的新Azure DevOps管道失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！