azure-pipelines-release-pipeline

问题 I am getting crazy to achieve this very simple task. I need to set an Output Variable in an Azure CLI task on Visual Studio Team Services, because next task in the Release definition will be executed according to the value of this variable. I wrote this simple code call az extension add --name azure-cli-iot-ext call echo ##vso[task.setvariable variable=iotEdgeExists;]$(az iot hub query -n $(iotHub) -q "select * from devices.modules where devices.deviceId ='$(iotEdge)'") which works, but not

问题 I have rather simple scenarion, one master branch then when I want to do a production release I want to tag a commit with eg. vX.X.X. The CI/CD pipeline looks like this Build -> Staging Environment -> Production Environment Every commit to master is sent to staging environment When I add a vX.X.X tag to a commit I want the staging and production environment to trigger. I have found this link Trigger build when pushing tag to git. I just can't figure it out how to make it work. It simply does

问题 I am following this process to create a YAML build pipeline for a .NET Core Web API project: https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-yaml?view=vsts When it comes to releasing it, I note that the (recently renamed) Azure DevOps doesn't seem to support YAML for defining release pipelines. However, I can see that deployment tasks have been defined eg: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-rm-web-app-deployment?view=vsts Are we

问题 What is the easiest way to get key rotation to work for azure storage accounts from a AzureDevOps relase task? The current plan is to re-generate the old key after release to invalidate it, and have a fresh key that can be used on next deployment. But to get that to work it seems like I at least need to store the name of the key to use in a release variable. I had a look at he logging tasks (https://github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/authoring/commands.md), but that