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 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."
"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."
"I wanted to monitor a hybrid cloud environment, one using AWS and Azure. If I have to provision/orchestrate between multiple cloud platforms, I can use Chef as a one-stop solution, to broker between those cloud platforms and orchestrate around them, rather than going directly into each of the cloud-vendors' consoles."
"The scalability of the product is quite nice."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"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 most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"Jenkins is very easy to use."
"Has enabled full automation of the company."
"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."
"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."
"We use Jenkins to automatically build Python binaries into several OS's i.e. OS X, Ubuntu, Windows 32-bit and Windows 64-bit."
"Having builds and test tasks triggered on commit helps not to break the product."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"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 agent on the server sometimes acts finicky."
"I would like to see more security features for Chef and more automation."
"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."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"If they can improve their software to support Docker containers, it would be for the best."
"The AWS monitoring, AWS X-Ray, and some other features could be improved."
"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."
"We need more licensed product integrations."
"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."
"There is no way for the cloud repositories to trigger Jenkins."
"The solution's UI can use a facelift and the logs can use more detailed information."
"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."
"This solution could be improved by removing the storage of unnecessary data such as the history of test deployments that were unsuccessful."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"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, 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.
