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."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."
"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 recipes are easy to write and move across different servers and environments."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"The most valuable feature is the language that it uses: Ruby."
"The most valuable feature is automation."
"It is a well thought out product which integrates well with what developers and customers are looking for."
"Jenkins has built good plugins and has a good security platform."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"The most valuable feature of the solution is its integration between different tools."
"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."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"Continuous Integration. Jenkins can integrate with almost any systems used for application development and testing, with its plugins."
"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."
"The most valuable feature is its ability to connect with different tools and technologies."
"Since we are heading to IoT, this product should consider anything related to this."
"It is an old technology."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"Support and pricing for Chef could be improved."
"The agent on the server sometimes acts finicky."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."
"We cannot change the ownership of any directory or file or any kind of directory."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"Sometimes you have Jenkins restarting because of OOM errors."
"It can be improved by including automated mobile reporting integrations."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
"Better and easy-to-use integration with Docker would be an improvement."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
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.
