Continuous Integration

Remote Run and Pre-Tested Commit

With TeamCity you can build your code, check it, and run automated tests on the server even before committing your changes — keeping your code base clean at all times.

These features are provided via IDE plugins for IntelliJ IDEA-based products, Microsoft Visual Studio and Eclipse.

Read more

Markdown Support

Problem and Test Management

Several persons can be assigned for investigation of problems in one build. For example, Jane researches why the process exited with code 1, while Bill fixes some tests.

When a problem is assigned, notification(s) are sent to the corresponding person(s).

Automatic assignment of investigations

Automatic Investigation Assignment

TeamCity will suggest or automatically assign investigations to team members based on a number of heuristics. That way the person who most likely broke a build will receive a notification to investigate the failure.

On-the-fly Test Reporting

On-the-fly Build Progress Reporting

TeamCity tracks different stages of the build and reports all the information on the fly - both in the web UI and in all supported IDEs. You don’t have to wait for a build to finish to discover that something is wrong.

TeamCity alerts you about failed tests immediately and provides details on encountered errors.

Flaky Tests

Flaky Tests

TeamCity detects tests which behave unstable with the same code. When such flaky tests are discovered based on a set of differents heuristics, they are displayed to you on a dedicated page, so that you can look into them or assign investigations to have your team members fix them.

Test metadata

Metadata in Test Results

Add screenshots and other test data, such as links, artifacts, logs, and numeric values, to the test results. These will be displayed natively in the test details section of the UI.

Newly Failed Tests

Newly Failed Tests and "Fixed in"

When newly checked-in code fails a test, TeamCity immediately shows it. If a test did not fail in the previous build, it will be shown as a "New" failed test.

For a failed test, you can see the build in which it failed for the first time and what changed in this build.

Risk Group Tests Reordering

For certain build tools like Ant, IDEA Project runner, MSBuild and some others, you can configure TeamCity to change order of tests.

For example, recently failed or new tests can be started before others to provide even faster feedback to the developer.


TeamCity offers multiple ways to instantly notify you about build problems or any other changes in your projects.

Be notified by email, instant messenger, Slack, or get notification right in your IDE.

You can set up multiple notification rules on all kinds of events, choose the order in which they are processed, and also edit, reuse, and share their settings using the Kotlin DSL.