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 simple."
"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."
"Jenkins has a lot of built-in packages and tools."
"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 solution is scalable and has a large number of plugins that can help you scale it to your needs."
"The automated elements are easy to use and you can put them into your server."
"It is a stable solution."
"It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature. It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
"TeamCity's GUI is nice."
"TeamCity is a very user-friendly tool."
"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."
"Good integration with IDE and JetBrains products."
"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."
"They need to improve their documentation."
"Sometimes you have Jenkins restarting because of OOM errors."
"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."
"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"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."
"It can be improved by including automated mobile reporting integrations."
"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."
"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 there was more documentation that was easier to locate, it would be helpful for users."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"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."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
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.