CircleCI vs TeamCity comparison

Cancel
You must select at least 2 products to compare!
CircleCI Logo
1,878 views|1,711 comparisons
66% willing to recommend
JetBrains Logo
3,373 views|2,977 comparisons
92% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between CircleCI and TeamCity based on real PeerSpot user reviews.

Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed CircleCI vs. TeamCity Report (Updated: March 2024).
768,415 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"It's a stable product.""Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts.""Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate.""The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications.""The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc.""The solution offers continuous integration and continuous delivery."

More CircleCI Pros →

"TeamCity is a very user-friendly tool.""Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end.""TeamCity's GUI is nice.""Good integration with IDE and JetBrains products.""The integration is a valuable feature.""VCS Trigger: Provides excellent source control support.""It's easy to move to a new release because of templates and meta-runners, and agent pooling.""We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."

More TeamCity Pros →

Cons
"The solution’s pricing could be better.""Billing is a mess.""Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing.""There needs to be some improvement in the user interface of CircleCI."

More CircleCI Cons →

"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs.""If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal.""I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does.""Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted.""It will benefit this solution if they keep up to date with other CI/CD systems out there.""Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone)​ to provide training classes to help newcomers get things up and running more quickly.""The upgrade process could be smoother. Upgrading major versions can often cause some pain.""If there was more documentation that was easier to locate, it would be helpful for users."

More TeamCity Cons →

Pricing and Cost Advice
  • "The price of CircleCI could be less expensive."
  • More CircleCI Pricing and Cost Advice →

  • "Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."
  • "The licensing is on an annual basis."
  • More TeamCity Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    768,415 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Top Answer:The solution offers continuous integration and continuous delivery.
    Top Answer:Beware of skyrocketing bills as CircleCI does not provide transparency into how they charge refills. Their monthly billing statement is almost unreadable and their online dashboard doesn't provide… more »
    Top Answer:We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup and environment. That costs us credits. Support engineers do not thoroughly read… more »
    Top Answer:TeamCity is a very user-friendly tool.
    Top Answer:It's open source, however, if you want your solution to be deployed on their cloud or on the cloud in general without you being involved and having it and managed by them, there may be costs involved… more »
    Top Answer:It's just a tool that I used. I needed to deliver something, so I did. I wasn't looking at it in a way to criticize it or to optimize it. As a user, I need some more graphical design. For example, in… more »
    Ranking
    11th
    out of 41 in Build Automation
    Views
    1,878
    Comparisons
    1,711
    Reviews
    2
    Average Words per Review
    342
    Rating
    4.0
    6th
    out of 41 in Build Automation
    Views
    3,373
    Comparisons
    2,977
    Reviews
    2
    Average Words per Review
    574
    Rating
    8.0
    Comparisons
    Tekton logo
    Compared 21% of the time.
    Jenkins logo
    Compared 10% of the time.
    GitHub Actions logo
    Compared 8% of the time.
    AWS CodeBuild logo
    Compared 6% of the time.
    GoCD logo
    Compared 4% of the time.
    GitLab logo
    Compared 44% of the time.
    Jenkins logo
    Compared 9% of the time.
    Harness logo
    Compared 6% of the time.
    Tekton logo
    Compared 6% of the time.
    GitHub Actions logo
    Compared 5% of the time.
    Learn More
    Overview
    CircleCI's continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. CircleCI offers a modern software development platform that lets teams ramp quickly, scale easily, and build confidently every day.

    TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.

    Sample Customers
    Shopify, Zenefits, Concur Technologies, CyberAgent
    Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company18%
    Financial Services Firm12%
    Comms Service Provider7%
    Manufacturing Company7%
    REVIEWERS
    Financial Services Firm13%
    Computer Software Company13%
    Non Tech Company7%
    Hospitality Company7%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company15%
    Manufacturing Company10%
    Comms Service Provider7%
    Company Size
    VISITORS READING REVIEWS
    Small Business26%
    Midsize Enterprise13%
    Large Enterprise61%
    REVIEWERS
    Small Business37%
    Midsize Enterprise15%
    Large Enterprise48%
    VISITORS READING REVIEWS
    Small Business25%
    Midsize Enterprise9%
    Large Enterprise66%
    Buyer's Guide
    CircleCI vs. TeamCity
    March 2024
    Find out what your peers are saying about CircleCI vs. TeamCity and other solutions. Updated: March 2024.
    768,415 professionals have used our research since 2012.

    CircleCI is ranked 11th in Build Automation with 5 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. CircleCI is rated 6.6, while TeamCity is rated 8.2. The top reviewer of CircleCI writes "Unhelpful support, unclear billing, and has offers ability to track usage". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". CircleCI is most compared with Tekton, Jenkins, GitHub Actions, AWS CodeBuild and GoCD, whereas TeamCity is most compared with GitLab, Jenkins, Harness, Tekton and GitHub Actions. See our CircleCI vs. TeamCity report.

    See our list of best Build Automation vendors.

    We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.