Try our new research platform with insights from 80,000+ expert users

CircleCI vs Jenkins vs TeamCity comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Mindshare comparison

As of August 2025, in the Build Automation category, the mindshare of CircleCI is 3.3%, down from 3.6% compared to the previous year. The mindshare of Jenkins is 10.3%, down from 12.2% compared to the previous year. The mindshare of TeamCity is 7.2%, up from 6.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

reviewer0972521 - PeerSpot reviewer
Unhelpful support, unclear billing, and has offers ability to track usage
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 and understand issues when emailing them. They reply to me with a totally different context about the problem. Just yesterday, my web applications failed to 'yarn build' after I downgraded the resource class from extr-large to large. I contacted support and got no reply. Billing is a mess. There is duplicate information in the bill downloaded from their website and when I asked for a consolidated bill, they just answered that they didn't have it. There is no transparency on how many billed minutes and credits I spent each day both on their website and the monthly bill which makes it difficult to understand when the monthly bill contains many refill item charges. It is difficult or impossible to track usage and burndown of my subscription and to gain total outstanding refill amounts on a daily basis. Their website doesn't provide sufficient information on credits allocated/calculated for my extra-large resource class.
Annamalai Pts - PeerSpot reviewer
Streamlined CI/CD pipelines with powerful integration and an easy setup
I use Jenkins as a CI/CD tool. We create pipelines using Jenkins, with stages for Maven builds, Docker image builds, SonarQube integration, and deploying the image to a Kubernetes cluster, AWS EKS Jenkins has made the developers' work very easy. They commit to the remote repository, and…
Almoeeni Fazal - PeerSpot reviewer
Impressive pipeline efficiency with helpful support and a fairly straightforward setup
We use TeamCity for the CI/CD pipeline. It is used for deploying code from the desktop to the production environment. We push our code to GitHub, which then creates a pipeline to a server using AWS, deploying automatically without errors or conflicts in GitHub branches.  We also use TeamCity's…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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 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."
"It's a stable product."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"Jenkins is very stable."
"Having builds and test tasks triggered on commit helps not to break the product."
"A lot of support material exists via a single web search of exactly what you're looking for."
"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."
"It offers continuous deployment and continuous testing. It enables us to figure out anything."
"The most valuable feature is its ability to connect with different tools and technologies."
"It's very easy to learn."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"TeamCity is more structured and user-friendly than other vendors."
"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
"It is very easy to use, and its speed is impressive, allowing the code to be ready for production in seconds."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"TeamCity's GUI is nice."
"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
"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."
"The integration is a valuable feature."
 

Cons

"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."
"Billing is a mess."
"The solution’s pricing could be better."
"There needs to be some improvement in the user interface of CircleCI."
"It would be helpful if they had a bit more interactive UI."
"Partition security for the workflow of projects is not yet an option."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"The solution could improve by having more advanced integrations."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests."
"It can be improved by including automated mobile reporting integrations."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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 like to see an improvement where TeamCity alerts us via email or another medium if there are discrepancies between the code in the staging environment and what has been deployed to production, such as missing updates."
"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 there was more documentation that was easier to locate, it would be helpful for users."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
 

Pricing and Cost Advice

"The price of CircleCI could be less expensive."
"Jenkins is open-source, so it is free."
"The tool is open-source."
"Jenkins is an open-source platform."
"In our company, we do pay for the licensing of the solution."
"It is an open source."
"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."
"Jenkins is a free solution, it is open source."
"The open-source version is free, but small companies would not be able to afford the cloud-based version."
"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."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Comparison Review

it_user184734 - PeerSpot reviewer
Jan 22, 2015
I generally find TeamCity a lot more intuitive than Jenkins.
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…
 

Top Industries

By visitors reading reviews
Computer Software Company
18%
Financial Services Firm
9%
Comms Service Provider
8%
Educational Organization
8%
Financial Services Firm
21%
Computer Software Company
14%
Manufacturing Company
13%
Government
7%
Financial Services Firm
21%
Computer Software Company
17%
Comms Service Provider
8%
University
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about CircleCI?
The solution offers continuous integration and continuous delivery.
What is your experience regarding pricing and costs for CircleCI?
Beware of skyrocketing bills as CircleCI does not provide transparency into how they charge refills. Their monthly bi...
What needs improvement with CircleCI?
We've had occasional connectivity issues with cloud resources and build failure due to its own internal system setup ...
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requi...
What do you like most about Jenkins?
Jenkins has been instrumental in automating our build and deployment processes.
What is your experience regarding pricing and costs for Jenkins?
Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of pro...
What do you like most about TeamCity?
One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to diff...
What is your experience regarding pricing and costs for TeamCity?
Compared to new technologies, TeamCity is more expensive and is an older tool compared to tools like GitLab.
What needs improvement with TeamCity?
TeamCity's user interface could be improved; specifically, the tree structure on the homepage is not clear, making it...
 

Comparisons

 

Overview

 

Sample Customers

Shopify, Zenefits, Concur Technologies, CyberAgent
Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: July 2025.
865,384 professionals have used our research since 2012.