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."It can scale easily."
"The most valuable feature is its ability to connect with different tools and technologies."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"Jenkins has excellent task planning features."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"Jenkins is very user-friendly."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"Good integration with IDE and JetBrains products."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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 very useful due to the fact that it has a strong plug-in system."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"TeamCity is a very user-friendly tool."
"VCS Trigger: Provides excellent source control support."
"TeamCity's GUI is nice."
"The solution's UI can use a facelift and the logs can use more detailed information."
"Jenkins takes a long time to create archive files."
"Jenkins needs a faster deployment process."
"The scriptwriting process could be improved in this solution in the future."
"The solution could improve by having more advanced integrations."
"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."
"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."
"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"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."
"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."
"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."
"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.