Book Image

Learning Continuous Integration with TeamCity

Book Image

Learning Continuous Integration with TeamCity

Overview of this book

Table of Contents (19 chapters)
Learning Continuous Integration with TeamCity
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Build history cleanup


As TeamCity continues to build our projects, the amount of disk space utilized by it keeps increasing. The artifacts, in particular, take up a lot of disk space. While disk space has become a lot cheaper these days, it is still not practical to let the disk usage keep increasing forever.

TeamCity has a very powerful cleanup feature that can be used to control how build history and artifacts are cleaned on the server. The cleanup is either run periodically or triggered manually. It can be configured for the server as a whole, while also overriding the settings, as needed, for individual projects and build configurations.

The Build history clean-up section can be reached from Administration | Build history clean-up (located in the left-hand side bar.) The following screenshot shows the settings page of this feature:

Under Clean-up settings, we can enable or disable Periodical clean-up. This is akin to running a cron job to clean up the history and artifacts at a particular...