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 automated elements are easy to use and you can put them into your server."
"Jenkins is very user-friendly."
"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."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"This is a great integration tool and very powerful."
"The initial setup is simple."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"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."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"Good integration with IDE and JetBrains products."
"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."
"Better and easy-to-use integration with Docker would be an improvement."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"A more user-friendly UI for creating pipelines would be helpful."
"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"The enterprise version is less stable than the open-source version."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
"I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"REST API support lacks many features in customization of builds, jobs, and settings."
"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."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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 need some more graphical design."
Jenkins is ranked 2nd in Build Automation with 83 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. Jenkins is rated 8.0, while TeamCity is rated 8.2. 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, GitHub Actions and Tekton. 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.
