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 Appsmith?

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

What is BiznessApps?

Bizness Apps is a mobile app platform enabling small businesses to easily create, edit, and manage applications online. This San Diego based platform founded in 2010 self-describes as a "do-it-yourself" iPhone, iPad, Android & HTML5 app platform that allows small business to build mobile apps or…

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 Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-3 of 3)

TeamCity 7 Years On!

Rating: 8 out of 10
May 25, 2018
SH
Vetted Review
Verified User
TeamCity
7 years of experience
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, both development and product support use it. It's the tool which pulls together the 300+ components that make up our current SaaS-based product and the tool which schedules, executes and produces reports for all our type of automation testing (behavioral, backward compatibility, performance, security, and load).
  • A very friendly UI with good drill-down and "Pro" capabilities compared to all other CI systems
  • A good reporting system that allows all our different types of automation tests to produce output for
  • Fantastically simple to setup and configure
Cons
  • The biggest and only issue we have is the lack of a SaaS-based TeamCity solution. Currently, we have to host and maintain 1 big TeamCity server and up to 15 build agents to build our 1500+ builds
If requiring a CI system and you have VMs available to host it yourself, TeamCity is a great choice.
  • We were able to ensure we're deploying the correct version of each component with ease and assurity
TeamCity by far has the best interface TeamCity still supported our old SubVersion reports as well.

A easy and clean continuous evaluation tool.

Rating: 9 out of 10
May 03, 2016
AS
Vetted Review
Verified User
TeamCity
1 year of experience
TeamCity was used by my team to do the continuous evaluation and integration of various projects under our team. It was used by our team only in our organisation. It was easy to spot wrong commits and build a failure before the product release. This was very easy with the help of a continuous integration tool like TeamCity that has a very versatile UI.
  • By default, the TeamCity installation comes with embedded Hypersonic SQL DB (HSQLDB for short). It is a good database in its own right and has its strengths in the situations where you would need a fast and tightly integrated in-process DBMS embedded into your Java application. But running a production server on HSQLDB is risky.
  • TeamCity offers much better security than Jenkins from out of box installation itself.
  • Browser-hosted interface serves as the primary way to administer TeamCity users, agents, projects, and build configurations. It provides project status and reporting information suitable for a broad range of users and project stakeholders. It provides build progress, drill down detail, and history information on the projects and configurations.
  • In TeamCity a single branch can be built dynamically. When configuring a Git or Mercurial VCS root, you need to specify the branch name to be used as the default.
Cons
  • TeamCity download was about 535 MB. Starting up TeamCity server on Mac is quite a large space.
  • When compared with the existing continuous integration tools the number of plug-ins available is much less for TeamCity.
They have better documentation and tutorials, a cleaner UI and dashboard and the easiest implementation. When a big team was working in the same repository we had to build every commit automatically and validate each committer and with TeamCity. The integration process was easy and it gave individual validation for individual committers.
  • TeamCity provides continuous integration, automated build and continuous deployment for a price. When compared with the pioneers in CI field, which are free software, TeamCity is effective because the implementation, familiarisation and integration time is less.
  • Effective hours to manage this tool is less, which increases the return on investment. But we have to pay while using for bigger number of projects is a drawback when there is free softwares in the market.
  • Easy implementation.
  • Cleaner dashboard and UI.
  • Better documentation and tutorials.

TeamCity above all else

Rating: 9 out of 10
May 07, 2019
Vetted Review
Verified User
TeamCity
2 years of experience
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.
  • 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.
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.
  • TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
  • TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
  • TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.
I would also like to compare TeamCity against Snap-Ci as well as Concourse. We chose TeamCity over all of these tools because of its ability to be set up easily against a restricting corporate firewall. We needed to integrate unit tests, integration tests, pushes to production, and Docker containers into our CI, but were not able to with the other tools. We found other teams in other departments were having great success with TeamCity so we decided to give it a try and had the same great success. Good documentation is key, and you will definitely find that with TeamCity. There are several extensions or tools available to further modify TeamCity to your needs, but it is an excellent tool out of the box.
TeamCity doesn't slow down when integrating with other tools. It's one of the faster CI tools I've seen. Pages load very quickly, reports are near instant, build logs and the pipeline images are live, and it handles anything we throw at it.
Return to navigation