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 initial setup is pretty simple."
"This is a great integration tool and very powerful."
"We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"The deployment of traditional Jenkins is easy."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."
"Good integration with IDE and JetBrains products."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"VCS Trigger: Provides excellent source control support."
"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."
"Some kind of SaaS product would be helpful in providing organizational structure."
"Better and easy-to-use integration with Docker would be an improvement."
"The solution's UI can use a facelift and the logs can use more detailed information."
"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."
"Jenkins needs a faster deployment process."
"The upgrades need improvement."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"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."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
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.