Skip to main content
TrustRadius
TeamCity

TeamCity

Overview

What is TeamCity?

TeamCity is a continuous integration server from Czeck company JetBrains.

Read more

Learn from top reviewers

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is TeamCity?

TeamCity is a continuous integration server from Czeck company JetBrains.

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.jetbrains.com/teamcity/buy

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

Alternatives Pricing

What is Codemagic?

Codemagic is a developer's CI/CD tool for mobile app projects. Build Android, iOS, React Native, Ionic, Unity, and Flutter projects on Codemagic.Codemagic uses its own CLI tools under the hood to perform complicated tasks like code signing and distribution to the stores. These are open-sourced and…

What is Appsmith?

Appsmith is an open source framework to build admin panels, CRUD apps and workflows.

Return to navigation

Product Demos

Sitecore CI/CD with TeamCity and TDS Demo

YouTube

Redgate DLM Demo (with TFS, TeamCity, & Octopus Deploy)

YouTube

CI/CD with JetBrains TeamCity | TeamCity Tutorial

YouTube

Demo Teamcity Build Project 2 (end)

YouTube

TeamCity Fundamental Tutorial for Beginners with Demo || Class - 01 || By Visualpath

YouTube

TeamCity demo - part 1

YouTube
Return to navigation

Product Details

What is TeamCity?

A Continuous Integration and Deployment server that provides out-of-the-box test intelligence, real-time reporting on build problems, and boasts scalability. It is available both as an on-premises and a cloud-based version.

TeamCity Video

Getting Started with TeamCity

TeamCity Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

TeamCity is a continuous integration server from Czeck company JetBrains.

Atlassian Bamboo, Jenkins, and CloudBees Continuous Integration are common alternatives for TeamCity.

The most common users of TeamCity are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-5 of 18)

Team City - An Easy to Use Continuous Integration Platform

Rating: 8 out of 10
May 17, 2018
EH
Vetted Review
Verified User
TeamCity
4 years of experience
We used TeamCity as our Core Continuous Integration solution for four years. I love TeamCity's easy to use interface, and the way builds and releases are linked together in dependency Chains. I found it particularly helpful that Builds can be run separately, or in advance of Releases - and then when Releases are run the Builds only run again if the code has changed. TeamCity's Templates, Variables, and Parameterization capabilities also made it very easy to establish a flexible template for common solutions such as deploying MVC applications to IIS. Once templates were configured I could create a "build and release" for a new project in less than 10 minutes.

While TeamCity has a simple to use and understand chaining mechanism, allowing builds to call "builds and releases" to rely on multiple dependency chains - TeamCity's PipeLine visualization capabilities are one of its weakest points. I had a complex build across five different environments consisting of eight different solutions and over 20 deployment targets. During a major update, it would have been nice to visualize the deployment pipeline and "watch" the deployment process for issues - but that really isn't possible with TeamCity. Outside of that, TeamCity worked great, integrated well with all of our platforms: Git, Azure, AWS, Visual Studio Team Services.

Great Product.
  • Build: Parameterization, Chaining from multiple sources, Templates, and general ease of use.
  • Release: Works extremely well with "Build" process.
  • Updates and Upgrades are simple, effective, and reliable.
Cons
  • Pipeline Visualization: TeamCity's weakest area
Small teams, Teams just getting started with Continuous Integration, or larger teams without the need for complex deployment pipeline visualization.

TeamCity is the ideal tool for agile teams using continuous integration

Rating: 8 out of 10
November 30, 2018
JK
Vetted Review
Verified User
TeamCity
3 years of experience
TeamCity was used by the technology department of the organization, especially by the web development team.

We used TeamCity to test and release code from our development environment to our production environment. Our web developers worked under an agile project management system and used continuous integration. In this system, TeamCity allowed us to integrate our git repository with our ticketing system, as well as help us quality assure and properly release clean code to production.
  • TeamCity provides a great integration with git, especially Bitbucket.
  • When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
  • TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.
Cons
  • Upgrading TeamCity is a long and manual process.
  • Java skills are needed to fully utilize TeamCity, although they are not necessary for basic or medium-level use.
TeamCity is well suited for an organization using continuous integration, meaning you release code to production often, and an agile project management system. There are free versions available for small teams and enterprise versions available for large teams with many different builds.

TeamCity is probably overkill for basic e-commerce or blog website builds that do not require much development after the initial launch.

TeamCity is an important part of our product pipeline

Rating: 8 out of 10
June 29, 2019
AA
Vetted Review
Verified User
TeamCity
3 years of experience
We use TeamCity on a self-hosted instance to build our ASP.NET projects, .NET desktop projects, and Angular projects. We use it to automatically build these various projects from our git repos and then execute deployment scripts via Octopus Deploy. We also run unit tests on each build and tie in build and test status to our code review tool, Upsource. TeamCity is part of our end-to-end pipeline that allows us to get quality changes out the door quickly and react to production issues quickly.
  • See build status across many projects.
  • It monitors multiple branches with different build processes for each.
  • It's a useful unit test runner with test history and identification of flaky or problematic tests.
Cons
  • Reading build output logs can be a pain at times, as they aren't really parsed; just long lines of output.
  • When you have multiple projects and branches, determining what is currently building, what is pending, and what has failed can be difficult.
TeamCity scales well for small teams. We run it on a low-cost instance with several other tools, and it performs well. It has some pretty straight forward build configurations, but can be expanded with scripts and various build settings. It might be a bit overkill for a single, small project, however.

My experience with TeamCity

Rating: 8 out of 10
August 03, 2018
RS
Vetted Review
Verified User
TeamCity
3 years of experience
TeamCity is the go-to tool to getting the Builds and Deployments packages for a variety of platforms like .NET, Java and JS etc. It is being used by the whole organization. It unifies the build and deployments needs of all the diverse projects to a single platform and solves the build and release issues previously we faced and reduces the time to go to Prod.
  • First and foremost is the ease of use
  • Very good support for extending , plugging and scripting support to customize your needs
  • Lightweight and accessible by browser.
Cons
  • The Debug log is quite verbose and could be made more intuitive for troubleshooting build errors
  • I would recommend improving it by some kind of integration with platforms like StackOverflow to aid developers and further improve the turnaround time for setting up successful builds
  • There is still scope for improvement for build integration with projects in AWS and Azure cloud platforms.
It is vary valuable to integrate the traditional .NET , JS, Java projects because of the maturity and the features the platform offers. There's a ton of options to extend the build and deployment process because of the support for scripting it provides. The learning curve is quite easy and the product is intuitive and very natural to understand.

TeamCity Delivers

Rating: 9 out of 10
August 13, 2021
Vetted Review
Verified User
TeamCity
4 years of experience
We make use of TeamCity to build and deploy our code from our git repositories to our various environments - development, test, staging, and production. We have incorporated comprehensive tests into the process as well, making TeamCity the backbone of our CI/CD pipeline that has strengthened our ability to deliver features.
  • The ability to have different build processes and monitoring per branch/environment
  • Run tests as part of the CI/CD pipeline
  • Status monitoring across multiple projects with build histories
Cons
  • When it is time to upgrade versions it is a cumbersome and time consuming process
  • Some of the reporting could be better, no real visualizations of pipelines, histories, etc.
TeamCity is well suiting for building and maintaining CI/CD pipelines across multiple branches and environments where each one can have unique build processes and steps. It is straightforward to incorporate tests into the process as well. Generally speaking, it performs well and scales with the business. If you are working with a simple, single project in one environment though you might want to look elsewhere as I think TeamCity might be overkill for your needs.
Return to navigation