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

TeamCity packs a mean punch for teams both big and small.

Rating: 10 out of 10
May 20, 2023
IncentivizedVetted ReviewVerified User
TeamCity is our primary build, test, and deploy automation tool. It is the key orchestration piece for the SDLC of more than 12 software products. TeamCity allows us to automa...
Continue reading
Verified user
Manager
TeamCity8 years of experience

TeamCity, a must for every team

Rating: 10 out of 10
August 16, 2021
IncentivizedVetted ReviewVerified User
TeamCity is used across all the development, test and DevOps departments across the company. It's integrated with every GitLab project to provide efficient continuous deployme...
Continue reading
BENAOUN Mahdi
Manager - Engineering
Software Developer
Primatec Engineering
TeamCity4 years of experience

TeamCity is an important part of our product pipeline

Rating: 8 out of 10
June 29, 2019
IncentivizedVetted ReviewVerified User
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 f...
Continue reading
Anthony Aziz
Engineer - Engineering
Senior Software Engineer
Full Circle TMS
TeamCity3 years of experience

TeamCity is the ideal tool for agile teams using continuous integration

Rating: 8 out of 10
November 30, 2018
IncentivizedVetted ReviewVerified User
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 en...
Continue reading
Jason Kelly
Manager - Information Technology
Data and Analytics Manager
American Institute for Economic Research
TeamCity3 years of experience

TeamCity 7 Years On!

Rating: 8 out of 10
May 25, 2018
IncentivizedVetted ReviewVerified User
Our company has two products. 1 of which, TeamCity is the critical tool for development and for both products, it's the critical tool for automation testing. In all cases, bot...
Continue reading
Simon Hurley
Manager - Research & Development
Development Manager
Elateral
TeamCity7 years of experience
Log in with LinkedIn to see content from your network
Return to navigation

Pricing

View all pricing
TeamCity

TeamCity

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

Appsmith

Appsmith

$250
per month
What is Appsmith?

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

Codemagic

Codemagic

Free
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…

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
View more demos
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 Competitors

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

View all reviews
(1-3 of 3)

Team City: Flexible, Distributed, Customizable build systems

Rating: 9 out of 10
Incentivized
May 16, 2018
LR
Larry Reed
Senior Software Engineer
Survey Monkey (Internet, 501-1000 employees)
Vetted Review
Verified User
TeamCity
5 years of experience
View profile
Use Cases and Deployment Scope
TC is used across our organization to do builds for all our apps and services. We started using it to replace our custom build and deploy system because we needed something more flexible and customizable, and something that did not need a fully dedicated support team.
Pros
  • Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
  • Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
  • Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.
Cons
  • The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
  • Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
Likelihood to Recommend
TC is great when you have a relatively straightforward sequence of build steps. It allows you to vary the set of build steps by application, and control the dependencies within the build steps.

For our needs, I haven't found any scenarios where TC doesn't provide what we need.
Return on Investment
  • When we initially started using it, there was a big impact because it made our build/deploy more reliable and flexible, as well as quicker.
  • Over time, we found that it was relatively easy to change our build and deployment system to our current Docker-based system. This has not only allowed us to continue improving our time to deploy but also to distribute the build process to engineers rather than have everything controlled by a dev infrastructure team.
  • Our most recent change has been to diversify our data centers to support international data centers. TC has made this process more or less seamless, although we no longer use it specifically for the deployment stage for various reasons.
Other Software Used
Docker, React

Team City - An Easy to Use Continuous Integration Platform

Rating: 8 out of 10
Incentivized
May 17, 2018
EH
Eric Huggins
Cloud Services Practice Manager and Principal Architect
Advanced Imaging Solutions (Information Technology and Services, 51-200 employees)
Vetted Review
Verified User
TeamCity
4 years of experience
View profile
Use Cases and Deployment Scope
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.
Pros
  • 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
Likelihood to Recommend
Small teams, Teams just getting started with Continuous Integration, or larger teams without the need for complex deployment pipeline visualization.
Return on Investment
  • TeamCity was a key contributor to our organization's adoption of Agile.
  • TeamCity made it possible to KILL "It works on my laptop" conversations with Developers. If it does not compile in TeamCity - the project is not deployable. TeamCity's easy to use interface made it possible to quickly adopt a "Deploy Only from TeamCity" policy, further ensuring TeamCity Builds were the gold-standard for well-configured source code.
Alternatives Considered
TeamCity is a great on-premise Continuous Integration tool.
Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud.
VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only.

TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
Other Software Used

One-stop solution for all build problems in massive organizations.

Rating: 9 out of 10
Incentivized
August 11, 2021
Verified User
Engineer in Research & Development
Financial Services Company, 10,001+ employees
Vetted Review
Verified User
TeamCity
2 years of experience
Use Cases and Deployment Scope
TeamCity is being used across my company. We have integrated TeamCity with the CI/CD pipeline. This is solving number of problems which occur if we do not have CI/CD in place. Configuring node servers to build the projects is easy. We can easily configure the properties while building the specific branch. Can easily build multiple feature/develop/release branches at once. It gives all build related information at one place, so can troubleshoot problem in build easily. Basic implementation of application is easy.
Pros
  • Selection of build server for specific build
  • We can add configurable properties
  • One stop solution to create deployable package
  • Initial and basic setup is easy
Cons
  • It is not plug and play thing
  • Need more specific configurations for smaller projects as well
  • Online help is less available
  • Basic implementation is easy but I think feature add on can be complex as it involve some language knowledge as well.
Likelihood to Recommend
Well suited :
1. Big organizations where we need central control on builds
2. Apply rules and regulations is central
3. Yet it can be configurable on every build
4. Add different supportive tools of development to find bugs, vulnerabilities.

Not Suited :
1. Small Organizations where no more regulation needed.
2. When no addition of supportive tools required we can end up writing complex config for simple solutions
3. For Start-ups it is not suitable as require specific experienced developer to handle it.
Most Important Features
  • Integrate with Sonar to highlight potential bugs
  • can be configured on big scale
  • We can add project specific settings/configurations.
  • Track all builds from your microservices architecture at one place.
Return on Investment
  • It is always better to have code quality check tolls integrated in CI/CD
  • For small projects also we have to go through same long path
  • This application is suitable for big microservices architecture, where we have many services
Alternatives Considered
This application is easy to install and deploy at site than most of the similar solutions in market. Easy user interface is one of the reason it can be installed. However each software have its good points and bad points. Study your organizations case and then only choose between applications.
Return to navigation