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 the language that it uses: Ruby."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"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."
"The product is useful for automating processes."
"The scalability of the product is quite nice."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"The most important thing is it can handle a 100,000 servers at the same time easily with no time constraints."
"Chef recipes are easy to write and move across different servers and environments."
"This solution has helped us in automating the build and test process, reducing time."
"It's very useful when you want to automate different processes from beginning to end."
"There are a large number of plugins available for integration with third party systems."
"Has a good interface, is reliable and saves time."
"The most valuable feature is its ability to connect with different tools and technologies."
"The most valuable feature of the solution is its integration between different tools."
"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"If they can improve their software to support Docker containers, it would be for the best."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"The agent on the server sometimes acts finicky."
"It is an old technology."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"I would like to see more security features for Chef and more automation."
"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."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"The documentation on plugin development could be better: more examples. "
"The support for the latest Java Runtime Environment should be improved."
"Jenkins should adopt the Pipeline as Code approach by building a deployment pipeline using the Jenkins file."
"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."
"There is no way for the cloud repositories to trigger Jenkins."
"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."
"The UI of Jenkins could improve."
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, BigFix, SaltStack and Microsoft Configuration Manager, whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and Digital.ai Release . 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.
