Blogroll

TeamCity offers a number of ways to help you work with tests. First of all, it presents the test results for each build execution so it’s easy to analyze what happened and why something has failed. Besides that, TeamCity includes advanced features like code coverage, flaky test detection, metadata i…

⚠️ Update from October 12, 2020: TeamCity TestDrive has been deprecated. If you are looking for a simple way to try TeamCity without downloading and installing it on a server, please consider giving a try to TeamCity Cloud. TeamCity Cloud is a fully-managed CI/CD solution that automati…

The support for pull requests in TeamCity was first implemented for GitHub as an external plugin. Starting with TeamCity version 2018.2 the plugin is bundled in the distribution package with no need to install the external plugin. The functionality has since been extended in version 2019.1 to suppor…

While TeamCity provides a lot of functionality out of the box and bundles a number of plugins in its distribution package, there are still use cases where you might need something extra. In this blog post, we are going to list 14 cool plugins that add new features or integrate with external tools. T…

Installing new plugins has just become a lot simpler! You don’t have to restart the server to enable a newly uploaded plugin anymore. The TeamCity server now integrates with the JetBrains Plugins Repository. The new integration simplifies the installation of plugins for TeamCity. By clicking t…

The Kotlin-based DSL is becoming more popular for defining build configurations in TeamCity. We are continuing to improve the user experience for Kotlin, both in the TeamCity UI and the IDE plugin. Once the versioned settings option is enabled for the project, we recommend making new changes in t…

Ever since TeamCity 2018.2, a test run in TeamCity can be associated with some supplementary information (metadata), in addition to a test’s status, execution time, and output. This information can be used to provide things like extra logs, screenshots, numeric values, and tags. You can now use s…

TeamCity 2018.1 allows you to set up a "running builds node." The node handles data coming in from the build agents. There's also the "read-only node" for handling disaster recovery scenarios. TeamCity 2018.2 expands this setup further, making it possible to delegate polling of version control sy…

The hassle with Pull Requests These days pull requests is a common technique of accepting changes from third-party contributors. In fact, it proved to be so convenient that some companies started to use it even for their regular development workflows. It is possible to configure TeamCity to run bui…

There is sometimes a need to define a common build step in a template, so that this step will be executed either before all build configuration steps or after them. Here’s a simple example. I’m building a lot of typical Maven projects, and for most of the part their build is the same: just run mv…

Enforcing some rules in a project might be quite useful to keep the things in order. For instance, enforce agent side checkout everywhere, or make sure that all build configurations have some strict execution timeout, or enable build files cleanup (Swabra) for all the builds. Starting with 2018.1…