Book Image

Microsoft Team Foundation Server 2015 Cookbook

By : Tarun Arora
Book Image

Microsoft Team Foundation Server 2015 Cookbook

By: Tarun Arora

Overview of this book

Team Foundation Server (TFS) allows you to manage code repositories, build processes, test infrastructure, and deploy labs. TFS supports your team, enabling you to connect, collaborate, and deliver on time. Microsoft's approach to Application Lifecycle Management (ALM) provides a flexible and agile environment that adapts to the needs of your team, removes barriers between roles, and streamlines processes. The book introduces you to creating and setting up team projects for scrum teams. You'll explore various source control repositories, branching, and merging activities, along with a demonstration of how to embed quality into every code check-in. Then, you'll discover agile project planning and management tools. Later, emphasis is given to the testing and release management features of TFS which facilitate the automation of the release pipeline in order to create potentially shippable increments. By the end of the book, you'll have learned to extend and customize TFS plugins to incorporate them into other platforms and enable teams to manage the software lifecycle effectively.
Table of Contents (16 chapters)
Microsoft Team Foundation Server 2015 Cookbook
Credits
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Index

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...