azure-pipelines-release-pipeline

I have some embedded C software stored under TFS and also have a corresponding TFS build definition that successfully checks out the code and builds it using the relevant compilers. So just to be clear, although this is TFS, I'm not building a .NET application. Now that I have the build working, I'm trying to provide overall software versioning support which should be linked to the build process. My current aim is as follows: The source code that is being built has a header file that has #defines for three variables, Major Version, Minor Version and Build Number. This header file is then used

I'm working with TFS on-premise. My issue is that during a release I have two agent phases separated by a manual intervention. In the first agent phase, I set a variable with: Write-Verbose $("##vso[task.setvariable variable={0};]{1}" -f $variablename, $variable) Problem is that in the second agent phase, this variable doesn't exist anymore, even if the same agent is used for the second release phase. How may I pass a variable between two agent phases during the same release? There is no way to persist variables (no matter powershell variables or VSTS user defined variables) between two agent

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 only changes the value in the current release and does not modify the release definition. You can use

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 not work for me. Is it possible and how do I configure the VSTS to start a build when a tag is added

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 expecting an upgrade to the release pipelines functionality to support YAML and, if so, when? Justin