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 really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"Jenkins's open-based framework is very valuable."
"The automated elements are easy to use and you can put them into your server."
"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."
"The initial setup is pretty simple."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"Jenkins is a very mature product."
"TeamCity is a very user-friendly tool."
"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."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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."
"The integration is a valuable feature."
"It could be cheaper."
"It can be improved by including automated mobile reporting integrations."
"The documentation is not helpful, as it is not user-friendly."
"Logging could be improved to offer a clearer view."
"Jenkins takes a long time to create archive files."
"I would like to see even more integrations included in the next release."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
"Partition security for the workflow of projects is not yet an option."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"REST API support lacks many features in customization of builds, jobs, and settings."
"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."
"I need some more graphical design."
"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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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 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.