Compare Jenkins vs. TeamCity

You must select at least 2 products to compare!
Jenkins Logo
12,144 views|9,611 comparisons
TeamCity Logo
3,413 views|2,639 comparisons
Most Helpful Review
Find out what your peers are saying about Jenkins vs. TeamCity and other solutions. Updated: January 2021.
464,369 professionals have used our research since 2012.
Quotes From Members

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

"There are a large number of plugins available for integration with third party systems.""The most valuable feature is its ability to connect with different tools and technologies.""It is very useful for us to be able to collect and manage automatic processing pipelines.""This solution has helped us in automating the build and test process, reducing time.""The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle.""A lot of support material exists via a single web search of exactly what you're looking for.""It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature. It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins."

More Jenkins Pros »

"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack.""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.""The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine.""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.""TeamCity is very useful due to the fact that it has a strong plug-in system."

More TeamCity Pros »

"The user interface could be updated a little.""This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager).""The learning curve is quite steep at the moment.""The upgrades need improvement.""Better and easy-to-use integration with Docker would be an improvement.""I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement.""Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."

More Jenkins Cons »

"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.""If there was more documentation that was easier to locate, it would be helpful for users.""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."

More TeamCity Cons »

Pricing and Cost Advice
"Jenkins is open source and free.""There is no cost. It is open source."

More Jenkins Pricing and Cost Advice »

Information Not Available
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
464,369 professionals have used our research since 2012.
out of 31 in Build Automation
Average Words per Review
out of 31 in Build Automation
Average Words per Review
Popular Comparisons
Learn More

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

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.

Learn more about Jenkins
Learn more about TeamCity
Sample Customers
Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
Toyota, Xerox, Apple, MIT, Volkswagen, HP, Twitter, Expedia
Top Industries
Computer Software Company42%
Media Company25%
Financial Services Firm17%
Computer Software Company32%
Comms Service Provider18%
Financial Services Firm11%
Manufacturing Company5%
Financial Services Firm22%
Leisure / Travel Company11%
Non Tech Company11%
Media Company11%
Computer Software Company27%
Comms Service Provider23%
Financial Services Firm13%
Manufacturing Company6%
Company Size
Small Business38%
Midsize Enterprise16%
Large Enterprise46%
Small Business38%
Midsize Enterprise19%
Large Enterprise43%
Find out what your peers are saying about Jenkins vs. TeamCity and other solutions. Updated: January 2021.
464,369 professionals have used our research since 2012.

Jenkins is ranked 1st in Build Automation with 8 reviews while TeamCity is ranked 3rd in Build Automation with 4 reviews. Jenkins is rated 8.0, while TeamCity is rated 8.6. The top reviewer of Jenkins writes "Useful for us to collect and manage automatic processing pipelines". On the other hand, the top reviewer of TeamCity writes "Scalable and simple to use with lots of very good plug-ins". Jenkins is most compared with Tekton, Harness, IBM Rational Build Forge, Release and GNU Make, whereas TeamCity is most compared with GitLab, Harness, Bamboo, Concourse for VMware Tanzu and IncrediBuild. See our Jenkins 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.