We performed a comparison between Jenkins 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."The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
"It is easy to use."
"Has enabled full automation of the company."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."
"Good integration with IDE and JetBrains products."
"TeamCity's GUI is nice."
"The integration is a valuable feature."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI."
"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."
"It would be helpful if they had a bit more interactive UI."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"The scriptwriting process could be improved in this solution in the future."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"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."
"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"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."
Jenkins is ranked 2nd in Build Automation with 83 reviews while TeamCity is ranked 6th in Build Automation with 24 reviews. Jenkins is rated 8.0, while TeamCity is rated 8.4. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Digital.ai Release , whereas TeamCity is most compared with GitLab, CircleCI, Harness, Tekton and Bamboo. 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.