Azure DevOps 上的触发器问题：最近检测到的一些与管道触发器相关的问题

Question

最近，我将 Azure DevOps CI 管道从经典的先前系统更新为新的 yaml 文件。看来我在正确设置触发器方面遇到了一些问题。

让我先向您展示错误消息，然后会给您完整的 yaml 文件。

我已经阅读了官方文档，并尝试通过多种变体来解决此问题，但我不明白。似乎什么都不起作用。

和细节

和我的 yaml 文件：

# ASP.NET
# Build and test ASP.NET projects.
# Add steps that publish symbols, save build artifacts, deploy, and more:
# https://learn.microsoft.com/azure/devops/pipelines/apps/aspnet/build-aspnet-4

trigger:
  branches:
   include:
     - master
     - release/*

pool:
  name: Hosted VS2017
  demands:
  - msbuild
  - visualstudio
  - vstest

name: 3.$(Date:yy).$(BuildID)

variables:
  
  buildPlatform: 'Any CPU'
  buildConfiguration: 'Release'

steps:
- task: NuGetToolInstaller@1
  displayName: 'Use NuGet 4.4.1'
  inputs:
    versionSpec: 4.4.1

- task: NuGetCommand@2
  displayName: 'NuGet restore'
  inputs:
    restoreSolution: $(Solution)

- task: VSBuild@1
  displayName: 'Build solution'
  inputs:
    solution: $(Solution)
    msbuildArgs: '/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.artifactstagingdirectory)\\"'
    platform: '$(BuildPlatform)'
    configuration: '$(BuildConfiguration)'

- task: VSTest@2
  displayName: 'Test Assemblies'
  inputs:
    testAssemblyVer2: |
     **\$(BuildConfiguration)\*test*.dll
     !**\obj\**
    platform: '$(BuildPlatform)'
    configuration: '$(BuildConfiguration)'
    diagnosticsEnabled: True

- task: PublishSymbols@2
  displayName: 'Publish symbols path'
  inputs:
    SearchPattern: '**\bin\**\*.pdb'
    PublishSymbols: false
  continueOnError: true

- task: PublishBuildArtifacts@1
  displayName: 'Publish Artifact'
  inputs:
    PathtoPublish: '$(build.artifactstagingdirectory)'
    ArtifactName: '$(Parameters.ArtifactName)'
  condition: succeededOrFailed()

这个触发部分出了什么问题。是因为“*”吗？

Answer 1

从昨天开始我们也无缘无故地收到这个问题。这似乎是 Azure DevOps 的一个错误，以下是 Microsoft 当前问题的链接： https: //developercommunity.visualstudio.com/t/Some-recent-issues-Detected-lated-to-p/1620293 ?space =21&q=一些+最近+问题+检测到+相关+至+管道+触发