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 automation."
"Deployment has become quick and orchestration is now easy."
"Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code."
"The scalability of the product is quite nice."
"The most valuable feature is the language that it uses: Ruby."
"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"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."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"It has a lot of community posts and support."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"Has a good interface, is reliable and saves time."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"The most valuable features of Jenkins are creating builds, and connecting them with Sonar for Sonar analysis. Additionally, we connect it with other vulnerability tools, such as WhiteSource which is useful."
"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."
"I would like to see more security features for Chef and more automation."
"Since we are heading to IoT, this product should consider anything related to this."
"The solution could improve in managing role-based access. This would be helpful."
"I would like them to add database specific items, configuration items, and migration tools. Not necessarily on the builder side or the actual setup of the system, but more of a migration package for your different database sets, such as MongoDB, your extenders, etc. I want to see how that would function with a transition out to AWS for Aurora services and any of the RDBMS packages."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"It is an old technology."
"The agent on the server sometimes acts finicky."
"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."
"In our case, we have several products built using Jenkins. It is quite difficult to navigate into the latest stable build in a given OS."
"There is no way for the cloud repositories to trigger Jenkins."
"A more user-friendly UI for creating pipelines would be helpful."
"The UI of Jenkins could improve."
"The UI must be more user-friendly."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"It would be helpful if they had a bit more interactive UI."
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.
