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."I like that you can find a wide range of plugins for Jenkins."
"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."
"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."
"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."
"Very easy to understand for newcomers."
"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."
"Jenkins has built good plugins and has a good security platform."
"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."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"VCS Trigger: Provides excellent source control support."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity's GUI is nice."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"The scriptwriting process could be improved in this solution in the future."
"The support for the latest Java Runtime Environment should be improved."
"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."
"The enterprise version is less stable than the open-source version."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
"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."
"The documentation is not helpful, as it is not user-friendly."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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 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."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
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 GitHub Actions. 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.