Setting Variable in Azure Pipeline for use in other Jobs doesn’t work as expected
We are setting a variable in Azure Pipeline that we want to use in another job but the variable is not visible in the other job. The following is a simplified YML files we are using with the outputs from the pipeline.
Azure DevOps – Get consumed artifacts for a YAML pipeline run via REST API
I have a YAML release pipeline which triggers from a build pipeline. I want to get the details about the consumed artifacts via REST API. E.g., Consumed artifacts of all types such as repositories, builds, etc as shown below:
Triggering an Azure DevOps pipeline from another pipeline that is triggered by a tag push
Base on this article /questions/60643528/triggering-an-azure-devops-pipeline-from-another-pipeline, I’m attempting to configure the dependent pipeline to run only when the source pipeline is triggered by a tag push. Below are the configurations for both pipelines:
chmod +x approach to run script in YML Azure Devops
I have started to practice how to create yml in azure devops. I have the following simple example I did.
Azure Devops Pipline
I need your assistance in creating an Azure DevOps pipeline that prompts the user for input during runtime. I want to incorporate five stages, and for each stage, I want the pipeline to ask the user if they want to continue or not. Based on their input, the stage will either run or be skipped.