Today when writing release notes for my customers latest release I bumped into an issue. I have a query that returns all item in the current Iteration Path with their release notes. The release notes are written in Microsoft Word so I thought that if I could just get the query into Excel it would be an easy “Copy and Past” operation into word.
Fortunately Azure DevOps have just this feature. You simply go to queries, click the three dots negt to the query and select Open in Excel
I had an issue today with one of my testcases in RSAT. When running it manyally from the RSAT UI it worked but when trying to run it from a PowerShell script I got this error:
Failed to download or overwrite attachment files – Some files maybe in use.
For some reason the test case uploaded duplicate files to Azure DevOps. When I ran the test in RSAT it uses the local file generated from RSAT and everything worked but when I ran it from the console it downloaded the files from DevOps, got the duplicates and for some reason failed.
The solution was to permanently delete the test case from DevOps and resync it from BPM.
Beware that that will give it another ID which will change the order of the tests.
In the project I am working on right now we are maintaining two release branches. One for sprint release and one for hotfixes. Every time we release a sprint we are re-targeting the the build pipelines to point to the new branches for the next sprint. This article is a short description for where you need to change path (mostly for me to remember):
Log into Azure DevOps
Go to Pipelines – Builds
Select the Pipeline you want to change and click Edit
Go to Get Sources and change the two fields under Server Path
Select the workflow item called Build the solution and change to the correct path in Project
Save the pipeline.
Note that when you are looking at the pipeline you will not see the correct branch until you have actually run the build successfully once
Today one of the test guys in our project asked if it was possible to get a notification when code was pushed to a specific branch in DevOps… specifically the branch that meant that they needed to test something… this is what you do:
Login into Azure Devops and go to User Setting – Notifications
Click New Subscription, choose Code (TFVC) and Code is checked in Note: since this is a Dynamics 365 FO project we are using TFVC
Set the Path (or other criteria) you want to check for and click finish
That is all…