I am working on vNext build in TFS Version 15.117.27414.0. I published the build artifacts to a shared file path. After I deleted the build record in history tab manually, why the drop folder of artifacts still exists in shared folder?
Asked
Active
Viewed 190 times
1 Answers
0
Tested on my side with TFS 2017 Update3 (TFS Version 15.117.27414.0) and the drop folder can be deleted successfully from the shared network path.
However the Parent folder (the Folder above the Drop folder) of the artifacts will not be deleted, it just delete the drop folder and it's contents.
If that still not work, just try to create a new build definition and try it again.
Andy Li-MSFT
- 28,712
- 2
- 33
- 55
-
Ok, i am trying to create another build and try again. – zgu Jun 27 '18 at 02:39
-
BTW, do you know how the build system detect the drop folder path when i delete the build record? – zgu Jun 27 '18 at 02:41
-
@zgu It should be set in Retention policies – Andy Li-MSFT Jun 27 '18 at 03:07
-
Thanks for reply, but I think my retention policy seems is correct. – zgu Jun 28 '18 at 05:16
-
@zgu Yeah, the `File Share` need to be selected in the retention policy. So can you reproduce the issue with the new builds? I mean create a new build definition and queue new builds, then check that again. – Andy Li-MSFT Jun 28 '18 at 06:08