Azure DevOps Server with YAML – build directory changes with every job?
Since moving everything YAML to a separate Git repo, I have an odd problem: Now, with every job in the pipeline, the directories on the agents change. The first job uses _work1, the second _work2, etc., meaning every job except the first fails, as the directories are empty.
How to link work items for a yaml pipeline build when using release branches?
In Azure DevOps, when using release (flow) branches along with YAML Build(+Release) pipelines. I’d like to be able to quickly identify a list of all the work items that are new/changed since the previous release.
Unable to Pass Variable between two stages targeting two Virtual Machines within YAML Pipeline
Over the last couple of days, I have been trying to get a variable to be passed from Stage 1 which runs on Server 1 via ADO Environment, to output on Stage 2 which is executed on another VM (Server2).
Environment variables as parameter of type object in Azure DevOps pipelines
I’m working on an Azure DevOps pipeline where I need to pass environment variables to a job template. Instead of passing these environment variables as a single string, I want to pass them as an object for better manageability.
Azure Pipeline – how to prevent circumvention of approval for environment?
Using a YAML-based Azure DevOps Pipeline, how do you require approval to deploy an app service (web app) to an environment such as Production in a way that can’t be circumvented by modification of the YAML?
Job Conditions in Azure Pipelines
In my yaml pipeline I have multiple jobs which are dependent on each other. However in one of the jobs when I define the condition, I am getting the following error:
Read template in parameters list Azure devops yaml
parameters: – name: XYZ type: object default: – template: “/Pipelines/Templates/QA/XYZ.yaml” – name: ZYX type: object default: – template: “/Pipelines/Templates/QA/ZYX.yaml” in the templates I have the parameters list like that: /Pipelines/Templates/QA/XYZ.yaml: – projectName: X display_name: Y – projectName: T display_name: R And it’s not reading the content… Is that the right way to implement template content […]
re-run run with a single stage
I know that it is possible to re-run a certain stage in yaml, but if my pipeline has a single stage, seems that the stage box (where the re-run button is) is not available. How can I re-run a single stage run?
Updating Node js on internal windows ADO build agent
I’m trying to run a pipeline on an internal hosted windows agent that needs version 12> of node.js but UseNode@1 task finds that version 10 is installed and skips doing anything else:
ADO YAML Pipelines | How to get secret variable from a variable group based on the value of another variable
In my project, i can get the value of a variable defined inside a variable group like this, without no problem