Using the build retention policy to automate build deletion
The build retention policy allows you to delete older builds including its output and related artifacts using a set of rules. The build retention policy in the old build system had two drawbacks:
The retention policy could only be applied per build definition
The retention was based on the number of builds only
The new build system allows a global retention policy; this makes it easier to administer build retention. The new system allows retention by the age of build, making it easier to create meaningful retention rules. In this recipe, you'll learn how to apply the build retention policy both globally at the Team Project Collection level and locally at the build definition level.
Getting ready
To administer build resources for the collection, you need to be a member of the Project Collection Build Administrators Group.
Scenario: The Fabrikam Team would like to enforce a default retention policy of 20 days across all build definitions...
