We performed a comparison between Chef and Nolio Release Automation based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Microsoft, Red Hat and others in Release Automation."This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"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."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"The product is useful for automating processes."
"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."
"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 is a well thought out product which integrates well with what developers and customers are looking for."
"Manual deployments came to a halt completely. Server provisioning became lightning fast. Chef-docker enabled us to have fewer sets of source code for different purposes. Configuration management was a breeze and all the servers were as good as immutable servers."
"The CA Application Insight feature is the solution's most valuable aspect."
"One standout aspect is its architecture. We can configure multiple instances on a single server using different system names or usernames."
"The graphical view of when you're writing flow is the most valuable feature."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"Chef could get better by being more widely available, adapting to different needs, and providing better documentation."
"Support and pricing for Chef could be improved."
"Vertical scalability is still good but the horizontal, adding more technologies, platforms, tools, integrations, Chef should take a look into that."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"Since we are heading to IoT, this product should consider anything related to this."
"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."
"There is a slight barrier to entry if you are used to using Ansible, since it is Ruby-based."
"The configuration of the solution is a bit difficult to maneuver. They should work to make it easier."
"It could use better integration with development tools."
"A concern with CA Release Automation is that Automic was acquired by CA recently. We're a bit concerned that CA strategy is going with Automic, that CA Release Automation is dead. They are not investing in it too much... They do say, that in the next two or three years we don't need to worry. They will still provide support for CA Release Automation. But we're not sure how CA Release Automation will evolve."
"In the next release, I would like to see more features to use active directory. And more rules to support more Python scripts and to work with Kubernetes and clouds, to have an easy solution for a lot of parameters."
"When I started using Nolio around eight months ago, a challenge was the lack of relevant information and related support for learning."
Chef is ranked 12th in Release Automation with 18 reviews while Nolio Release Automation is ranked 13th in Release Automation with 50 reviews. Chef is rated 8.0, while Nolio Release Automation is rated 7.8. The top reviewer of Chef writes "Useful for large infrastructure, reliable, but steep learning cureve". On the other hand, the top reviewer of Nolio Release Automation writes " Enables one-touch application deployment across various environments". Chef is most compared with Jenkins, Microsoft Azure DevOps, AWS Systems Manager, Microsoft Configuration Manager and UrbanCode Deploy, whereas Nolio Release Automation is most compared with GitLab, Red Hat Ansible Automation Platform, Microsoft Azure DevOps, UrbanCode Deploy and Automic Continuous Delivery Automation.
See our list of best Release Automation vendors.
We monitor all Release 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.