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
That is it for today…
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…
This is mostly a checklist for me to remember how to add new Sprints (Iteration Paths) in Azure DevOps… I tend to forget since it is not done very often
- Go to Project Settings in Azure DevOps
- In Project Confiruration choose the parent Iteration Path and click New Child
- Add Name, Start date and End Date and click Save and Close
- To mage the Sprint visible you need to add is to a team (otherwise noone will see it). To do this go to Team Configuration, choose Iterations and click Select Iterations.
- Choose the new sprint and click Save and Close
That is it for today… have a nice Monday
Yesterday evening (why does it always have to be evenings 😉 ) I was going to do a deploy of code to our staging environment. I started the build in Azure Devops and it failed:
C:\DynamicsSDK\Metadata\Microsoft.Dynamics.AX.Application.Build.targets(78,5): error MSB6006: “LabelC.exe” exited with code -1. [C:\DynamicsSDK\Metadata\BuildMetadata.proj]
OK… SO LabelC.exe atleast gives me some hints and since the deployconsisted of changes to Label Files this was not too strange. I downloaded the log file and found this information:
So I looked in the log file on the build server and found the following:
The error was duplicate lines in two label files
Remove them by editing the file in Azure DevOps and check in the file. Restart the build and it worked… Way