I am looking at this example from the msft docs:

So far I was using the below pipeline which triggers the main pipeline. It tracks the pushed tags by developer to the master branch, and if so, starts running.

Download Pipeline Artifacts shortcut: cannot resolve source name

I have 2 template files that I am passing to another (stage) template (file: build-and-deploy.yml) that’s in another repo (repoB) and I am doing this from azure-pipeline.yml which is in repoA. Once in repoB, depending on the option selected during the pipeline run, build-and-deploy.yml will call two other (stage) templates 0.yml or 1.yml. Unless I hard code the 2 templates in build-and-deploy.yml, I am unable to achieve this. The

I have 2 template files that I am passing to another (stage) template (file: build-and-deploy.yml) that’s in another repo (repoB) and I am doing this from azure-pipeline.yml which is in repoA. Once in repoB, depending on the option selected during the pipeline run, build-and-deploy.yml will call two other (stage) templates 0.yml or 1.yml. Unless I hard code the 2 templates in build-and-deploy.yml, I am unable to achieve this. The

I have 2 template files that I am passing to another (stage) template (file: build-and-deploy.yml) that’s in another repo (repoB) and I am doing this from azure-pipeline.yml which is in repoA. Once in repoB, depending on the option selected during the pipeline run, build-and-deploy.yml will call two other (stage) templates 0.yml or 1.yml. Unless I hard code the 2 templates in build-and-deploy.yml, I am unable to achieve this. The

I have 2 template files that I am passing to another (stage) template (file: build-and-deploy.yml) that’s in another repo (repoB) and I am doing this from azure-pipeline.yml which is in repoA. Once in repoB, depending on the option selected during the pipeline run, build-and-deploy.yml will call two other (stage) templates 0.yml or 1.yml. Unless I hard code the 2 templates in build-and-deploy.yml, I am unable to achieve this. The

– stage: PublishStage dependsOn: [PreStage, CheckTestProjects, TestStage] condition: | and( succeeded(), or( eq(dependencies.TestStage.result, ‘succeeded’), eq(dependencies.TestStage.result, ‘skipped’) ) ) jobs: – template: PublishNuget_jobs_template.yml@templates parameters: buildConfiguration: ‘${{ variables.buildConfiguration }}’ feed: ‘${{ variables.feed }}’ The pipeline always skips the publish stage. What i would like to achieve: If the TestStage was skipped (for eg.: testproject did not exist) […]

– stage: PublishStage dependsOn: [PreStage, CheckTestProjects, TestStage] condition: | and( succeeded(), or( eq(dependencies.TestStage.result, ‘succeeded’), eq(dependencies.TestStage.result, ‘skipped’) ) ) jobs: – template: PublishNuget_jobs_template.yml@templates parameters: buildConfiguration: ‘${{ variables.buildConfiguration }}’ feed: ‘${{ variables.feed }}’ The pipeline always skips the publish stage. What i would like to achieve: If the TestStage was skipped (for eg.: testproject did not exist) […]

– stage: PublishStage dependsOn: [PreStage, CheckTestProjects, TestStage] condition: | and( succeeded(), or( eq(dependencies.TestStage.result, ‘succeeded’), eq(dependencies.TestStage.result, ‘skipped’) ) ) jobs: – template: PublishNuget_jobs_template.yml@templates parameters: buildConfiguration: ‘${{ variables.buildConfiguration }}’ feed: ‘${{ variables.feed }}’ The pipeline always skips the publish stage. What i would like to achieve: If the TestStage was skipped (for eg.: testproject did not exist) […]