Reputation: 18485
Recently I updated my Azure DevOps CI pipeline from the classic previous system to the new yaml file. It seems I have some issue to properly setup the trigger.
Let me show you the error message first then a will give you my full yaml file.
I already read the official documentation and already tried to fix this with many variations but I don't get it. Nothing seems to work.
and the details
and my yaml file:
# 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()
What is wrong in this trigger section. Is it because of the '*'?
Upvotes: 4
Views: 3409
Reputation: 331
We're getting this issue too since yesterday for no reason. This appears to be a bug with Azure DevOps, here is a link to an issue currently with Microsoft: https://developercommunity.visualstudio.com/t/Some-recent-issues-detected-related-to-p/1620293?space=21&q=Some+recent+issues+detected+related+to+pipeline+trigger
Upvotes: 7