Thursday, December 08, 2011 12:30 PM
Within one of our customers, we have developed a custom build template (based on the default build template from tfs 2010).
What we experience is that often the drop output is deleted from the latest build although the retention policy is set to keep the latest 10 builds. When we set the retention policy on 'Keep all', the drop output is kept.
- who (process/service) is handling the retention policy? Is this a part of the build workflow?
- is the name of our build definition used in this algoritm ?
- is there some lecture which explains in detail how this is implemented in TFS 2010?
Friday, December 09, 2011 10:22 AMModerator
Thanks for your post.
· I am currently looking into this issue and will give you an update as soon as possible.
If you have any further research of this issue, please share your experience here.
John Qiao [MSFT]
MSDN Community Support | Feedback to us
Tuesday, January 31, 2012 10:39 AM
Can you please check the "What to delete" column on your case? What is the setting when you set "keep the latest 10 builds"?
Sophia Lu [MSFT]
Tuesday, January 31, 2012 3:17 PM
Yes, this problem occurs only when we specify a number of builds. In our case is was the latest 5 builds...
What to Delete = All
Wednesday, February 15, 2012 10:01 AM
Please refer another post.
Sophia Lu [MSFT]
Friday, August 24, 2012 8:14 AM
this give not an answer to my inital question.
If we specify 'Keep latest 10 builds', we encounter that the running build (the 11th build) deletes the build output of the 11th build... So my initial question was: how does the build retention policy determine if a build is in scope or not for deletion? Based on the name, submit time of other meta fields?