We performed a comparison between Chef 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 scalability of the product is quite nice."
"The product is useful for automating processes."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"Automation is everything. Having so many servers in production, many of our processes won't work nor scale. So, we look for tools to help us automate the process, and Chef is one of them."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"Stable and scalable configuration management and automation tool. Installing it is easy. Its most valuable feature is its compliance, e.g. it's very good."
"Good integration with IDE and JetBrains products."
"VCS Trigger: Provides excellent source control support."
"TeamCity is a very user-friendly tool."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"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."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"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 solution could improve in managing role-based access. This would be helpful."
"In the future, Chef could develop a docker container or docker images."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"Since we are heading to IoT, this product should consider anything related to this."
"I would also like to see more analytics and reporting features. Currently, the analytics and reporting features are limited. I'll have to start building my own custom solution with Power BI or Tableau or something like that. If it came with built-in analytics and reporting features that would be great."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"Support and pricing for Chef could be improved."
"They could provide more features, so the recipes could be developed in a simpler and faster way. There is still a lot of room for improvement, providing better functionalities when creating recipes."
"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."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"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."
"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."
Chef is ranked 13th in Build Automation with 18 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. Chef is rated 8.0, while TeamCity is rated 8.2. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Chef is most compared with Jenkins, AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager and BigFix, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and Tekton. See our Chef 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.
