Using job output variables in Azure Pipeline condition
I have a multiple pipelines which trigger a deployment pipeline with multiple different deployments. I would like to be able to conditionally run deployments based on what pipeline has triggered the run. To test the logic I’m trying to add a condition to a job, which should prevent running the job when triggering pipeline was build-arm
.
Using job output variables in Azure Pipeline condition
I have a multiple pipelines which trigger a deployment pipeline with multiple different deployments. I would like to be able to conditionally run deployments based on what pipeline has triggered the run. To test the logic I’m trying to add a condition to a job, which should prevent running the job when triggering pipeline was build-arm
.
Using job output variables in Azure Pipeline condition
I have a multiple pipelines which trigger a deployment pipeline with multiple different deployments. I would like to be able to conditionally run deployments based on what pipeline has triggered the run. To test the logic I’m trying to add a condition to a job, which should prevent running the job when triggering pipeline was build-arm
.
Using job output variables in Azure Pipeline condition
I have a multiple pipelines which trigger a deployment pipeline with multiple different deployments. I would like to be able to conditionally run deployments based on what pipeline has triggered the run. To test the logic I’m trying to add a condition to a job, which should prevent running the job when triggering pipeline was build-arm
.
Replace multiple characters in Azure pipeline parameters
We have a condition in our template to replace “parameter.reponame” if it has a “-” to an underscore “_” .
Is there any way in which I can also replace “.” to an underscore “_” if it exists in a repo name.
Adding multiple resources in YAML file
My YAML file already contains a Resource section and now I want to add a pipeline to the resource section to trigger my publish pipeline after the PR pipeline is successful. THis works fine and the pipeline is trigger when a merge is made to the main branch