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 features of Jenkins are the integration with GitHub, and the automation for deployment."
"Jenkins has built good plugins and has a good security platform."
"It has a lot of community posts and support."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"Jenkins has excellent task planning features."
"The most valuable feature of Jenkins is its continuous deployment. We can deploy to multi-cluster and multi-regions in the cloud."
"The initial setup is pretty simple."
"This is a great integration tool and very powerful."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"TeamCity's GUI is nice."
"TeamCity is a very user-friendly tool."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"The integration is a valuable feature."
"A more user-friendly UI for creating pipelines would be helpful."
"The documentation is not helpful, as it is not user-friendly."
"I would like to see even more integrations included in the next release."
"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."
"UI is quite outdated."
"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."
"Jenkins could improve the integration with other platforms."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
"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."
"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."
"I need some more graphical design."
Jenkins is ranked 2nd in Build Automation with 44 reviews while TeamCity is ranked 5th in Build Automation with 4 reviews. Jenkins is rated 7.8, while TeamCity is rated 8.0. The top reviewer of Jenkins writes "We can do whatever we want and customize as much as we wish to in any programming language". On the other hand, the top reviewer of TeamCity writes "User-friendly and easy to configure, but needs better UI". Jenkins is most compared with Tekton, Bamboo, GitLab, AWS CodePipeline and Concourse for VMware Tanzu, whereas TeamCity is most compared with GitLab, CircleCI, Harness, Tekton and AWS CodePipeline. 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.
