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."Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."
"Jenkins is very easy to use."
"Jenkins is very user-friendly."
"The most valuable features of Jenkins are the ease of use and the information about how to use the features is readily available on the internet. Additionally, with the solution, I can use other reporting tools, such as Flow."
"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."
"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."
"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."
"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."
"VCS Trigger: Provides excellent source control support."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity's GUI is nice."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"TeamCity is a very user-friendly tool."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"The solution could improve by having more advanced integrations."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"It would be helpful if they had a bit more interactive UI."
"Partition security for the workflow of projects is not yet an option."
"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."
"Jenkins needs a faster deployment process."
"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."
"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."
"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 need some more graphical design."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"If there was more documentation that was easier to locate, it would be helpful for users."
"REST API support lacks many features in customization of builds, jobs, and settings."
"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."
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.
