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."When we have manual tasks, we have to depend on multiple technical teams. With Jenkins, we can bring all the technologies together by the click of a button. We can see results without having to depend on different teams. Jenkins makes life easy for the database and DevOps teams."
"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."
"Jenkins has built good plugins and has a good security platform."
"The most valuable feature is its ability to connect with different tools and technologies."
"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline."
"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."
"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."
"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."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"TeamCity is a very user-friendly tool."
"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."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"TeamCity's GUI is nice."
"Good integration with IDE and JetBrains products."
"The integration is a valuable feature."
"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."
"Logging could be improved to offer a clearer view."
"The documentation on plugin development could be better: more examples. "
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"Centralized user management would be helpful."
"The enterprise version is less stable than the open-source version."
"The UI must be more user-friendly."
"We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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."
"I need some more graphical design."
"REST API support lacks many features in customization of builds, jobs, and settings."
"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."
"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."
"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 AWS CodeBuild, whereas TeamCity is most compared with GitLab, CircleCI, GitHub Actions, Harness 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.
