Concepts like templates and Meta-Runners help in managing lots of build configurations without introducing duplicated settings. Artifacts and build history cleanup ensure that the TeamCity server can continue to run forever without having to worry about running out of disk space.

Commenting, tagging, and pinning builds help in improving the discoverability of builds and provide extra information about them. Service messages help us to integrate new and custom tools with TeamCity, thereby bringing them on par with tools that are supported out of the box.

Build queue priority classes help us to ensure that builds are scheduled in an efficient manner and are not starved of agents.

These advanced concepts help us in tweaking and fine-tuning TeamCity to a great extent, thereby making it all the more easy for us to set up a long-running and well-oiled CI process.

In the next chapter, we will take a look at what's beyond CI, enter the world of Continuous Delivery (CD), and see how TeamCity...