Azure pipeline for multistage
– 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) […]
Azure pipeline for multistage
– 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) […]
ADO YAML template’s pipeline trigger is not being honored?
We have a YAML template pipeline that begins with the following:
How to Pass ADO Library to Azure Container Apps
The reference for AzureContainerApps@1 contains an argument environmentVariables which takes a string in space-separated {key}={value} format.
Check run variables on an if statement
I am trying to check the value of a variable that is set when running.
Dependant pipeline can’t continue deployment
I have a pipeline (MainPipeline) which triggers another one (DependantPipeline).
Dependant pipeline can’t continue deployment
I have a pipeline (MainPipeline) which triggers another one (DependantPipeline).
Passing artifacts between pipelines
The DependantPipeline (which is triggered by the another pipeline: MainPipeline) causes errors on Azure DevOps:
Azure DevOps YAML – can I trigger a job on another agent?
Currently my DevOps pipeline uses two servers to run things in parallel:
Is there any way to create reusable and scalable build and deployment pipeline(s) for similar services in an Azure DevOps environment?
and apoligies in advance for not being able to keep this any shorter.
I’m working with my team on a relatively large structure of related services (/ microservices) all hosted on Docker containers, working in a tandem. As our work has progressed, progressively more services have been added, and old legacy systems have even been rebuilt to fit our newer standards, making more of our internal IT structure transparent to people working on our development team.