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

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…

Appsmith

Appsmith

$250
per month
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
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-5 of 18)

Build with Confidence!

Rating: 10 out of 10
Incentivized
October 25, 2017
Verified User
Consultant in Information Technology
Information Technology and Services Company, 1-10 employees
Vetted Review
Verified User
TeamCity
5 years of experience
Use Cases and Deployment Scope
We use TeamCity for Continuous Integration & Delivery of our software products. We have many projects for various customers that are built and integrated continuously whenever we check code into our git repositories.

We use a mixture of Gradle & Maven builds and TeamCity handles both well.

We get immediate feedback from TeamCity if a code change has caused issues with other linked projects and, because we have confidence in our tests we also have confidence in a 'green' build prior to delivery to a customer.
Pros
  • Easy to set up. The UI is pretty easy to navigate and use. You can have your project up and running in minutes.
  • Good integration with various build frameworks/methodologies. You can run standard Maven, Ant or Gradle builds with virtually no customization.
  • Decent support for extensions via the plug-in mechanism. You can integrate with other popular tools such as Artifactory via plug-ins. Or write your own.
Cons
  • Upgrade process can be a bit of a pain - have to do this manually on your server.
  • It's easy for the new user to get lost in the UI. Although this is true for most systems that offer such a wide range of configuration options.
Likelihood to Recommend
If you're an Agile shop that does TDD & regular releases then it's great.

I'd recommend this even for solo Agile developers as the free version gives you three build agents and you can put everything on a spare machine and run the whole thing in Docker.



TeamCity - My Go-To Build system

Rating: 8 out of 10
Incentivized
April 14, 2017
CB
Christopher Belanger
Senior Software Engineer
Amadeus Hospitality (Computer Software, 1-10 employees)
Vetted Review
Verified User
TeamCity
4 years of experience
View profile
Use Cases and Deployment Scope
I set up TeamCity for our core product continuous integration. For both the main product and the core libraries it is used to compile on check in, build and deploy on pull requests, and to run the unit and functional tests. No code goes into the develop or main branches without passing through this process.
Pros
  • Ease of configuration. Some build systems are difficult to get started on. TeamCity can be up and running quickly.
  • Cross platform. TeamCity runs on most configurations, and a master can configure agents of other OS types, so it can build nearly anything.
  • Price. It's free for limited use, so you don't need to pay until you ramp up and are using it a lot.
Cons
  • The upgrade process could be smoother. Moving from one major version to another involves jumping onto all your servers and often causes some pain.
  • Log formatting could be a little clearer, though that is true for almost all build systems.
Likelihood to Recommend
Any time you are pushing code, you should be building continuously. TeamCity, like all JetBrains products, is well designed, well supported, and easy to use. I've found no other system that works as well cross-platform. If you don't have CI, you need it and should look at TeamCity.

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.

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.

TeamCity above all else

Rating: 9 out of 10
Incentivized
May 07, 2019
Verified User
Engineer in Information Technology
Computer Software Company, 10,001+ employees
Vetted Review
Verified User
TeamCity
2 years of experience
Use Cases and Deployment Scope
We use TeamCity as a CI/CD tool for our pre-production and production builds. We've set it up for near full automation use and have set it up with multiple steps for each build. TeamCity is used on a team-by-team basis here at my work. Several surrounding teams in many different departments use it with much success. TeamCity solves the problem of integrating other tools in the CI/CD build process without being too complicated or without too much overhead. Given a corporate firewall can cause great limitations, it's nice to have a tool that's simple to integrate with other tools.
Pros
  • Build Automation: easy setup, one-click deployment, reliable use, great documentation/instruction.
  • Tool Integration: great documentation, several existing examples, easy setup.
  • Step tracking: clear pipeline display, easy to locate build logs, clear error messages.
Cons
  • Desktop app: TeamCity is browser-based, and some may prefer having a desktop application to view deployments on.
  • Tasteful UI: TeamCity has a simple, non-graphic UI that some may find boring or not as intriguing as some of the other options.
Likelihood to Recommend
TeamCity is perfect for what it's advertised to do. It's a great pipeline tool that offers several benefits over other tools. What it lacks in a tasteful UI but it makes up for it in functionality, ease of setup, integration with other tools, and one-click operation if set up correctly. Setting up triggers from Github or your favorite source control is very simple, and connecting it to your production deployment is just as easy.
Return to navigation