Share
Report
11Hi there,
I am a developer for a D365 end user. We have a single model that is in an azure devops repo and we have a nightly build process that gets the latest from our repo and creates a build that can be deployed to our test environments via a release pipeline. I've noticed a few times now, if we delete an object from our repo, often times our build process will fail as the xml file for that object seems to still be in our build machine and the build process tries to compile it. We believe we tracked this down to a backup, stored in the J drive of our build machine containing that file and that file is being copied to the K drive where the build occurs. Then the latest from our repo is copied to the K drive, updating all the files with the latest but not removing the deleted file and hence causing the error when the compile process happens. I'm sure it's an issue on our end but I don't understand, why is this file in the backup on the J drive? What is the actual purpose of the backup on the J drive? Should the backup on the J drive contain all of the folders in the K://AosService//PackagesLocalDirectory EXCEPT for the folder for my model? We got around this a few times by deleting our model folder from both the J and the K drive on the build machine and we got a successful compile but then a month or so later when somebody deleted another file the same issue happened again. Does anyone have any idea what is the purpose of the backup that is stored in J and restored to K before the latest code is copied over the top and compiled? Thanks in advance for any light anyone can shed on this!
I am a developer for a D365 end user. We have a single model that is in an azure devops repo and we have a nightly build process that gets the latest from our repo and creates a build that can be deployed to our test environments via a release pipeline. I've noticed a few times now, if we delete an object from our repo, often times our build process will fail as the xml file for that object seems to still be in our build machine and the build process tries to compile it. We believe we tracked this down to a backup, stored in the J drive of our build machine containing that file and that file is being copied to the K drive where the build occurs. Then the latest from our repo is copied to the K drive, updating all the files with the latest but not removing the deleted file and hence causing the error when the compile process happens. I'm sure it's an issue on our end but I don't understand, why is this file in the backup on the J drive? What is the actual purpose of the backup on the J drive? Should the backup on the J drive contain all of the folders in the K://AosService//PackagesLocalDirectory EXCEPT for the folder for my model? We got around this a few times by deleting our model folder from both the J and the K drive on the build machine and we got a successful compile but then a month or so later when somebody deleted another file the same issue happened again. Does anyone have any idea what is the purpose of the backup that is stored in J and restored to K before the latest code is copied over the top and compiled? Thanks in advance for any light anyone can shed on this!
Adam
All responses (
Answers (
