We performed a comparison between Chef and Jenkins 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 most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"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 has been very easy to tie it into our build and deploy automation for production release work, etc. All the Chef pieces more or less run themselves."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"The most valuable feature is the language that it uses: Ruby."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"Chef recipes are easy to write and move across different servers and environments."
"We have had less production issues since using Chef to automate our provisioning."
"It is a stable solution."
"It has a lot of community posts and support."
"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"Has a good interface, is reliable and saves time."
"The deployment of traditional Jenkins is easy."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"The solution could improve in managing role-based access. This would be helpful."
"Since we are heading to IoT, this product should consider anything related to this."
"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."
"The agent on the server sometimes acts finicky."
"In the future, Chef could develop a docker container or docker images."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"Jenkins relies on the old version of interface for configuration management. This needs improvement."
"Support should be provided at no cost, as there is no free support available for any of the free versions."
"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 scriptwriting process could be improved in this solution in the future."
"Better and easy-to-use integration with Docker would be an improvement."
"We need more licensed product integrations."
"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."
"We cannot change the ownership of any directory or file or any kind of directory."
Chef is ranked 15th in Build Automation with 18 reviews while Jenkins is ranked 2nd in Build Automation with 83 reviews. Chef is rated 8.0, while Jenkins is rated 8.0. The top reviewer of Chef writes "Easy configuration management, optimization abilities, and complete infrastructure and application automation". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". Chef is most compared with AWS Systems Manager, Microsoft Azure DevOps, Microsoft Configuration Manager, SaltStack and BigFix, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and AWS CodeBuild. See our Chef vs. Jenkins 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.
