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."We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"I like that you can find a wide range of plugins for Jenkins."
"Having builds and test tasks triggered on commit helps not to break the product."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins."
"It can scale easily."
"Jenkins is very stable."
"It's very useful when you want to automate different processes from beginning to 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."
"TeamCity is a very user-friendly tool."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"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."
"VCS Trigger: Provides excellent source control support."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity's GUI is nice."
"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."
"I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"The solution's UI can use a facelift and the logs can use more detailed information."
"The documentation is not helpful, as it is not user-friendly."
"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."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"Jenkins could improve the integration with other platforms."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
"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 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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
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, 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.
