We performed a comparison between Automic Continuous Delivery Director and Red Hat Ansible Automation Platform based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation."The most valuable features of Automic Continuous Delivery Director are the UI, release planning, and tracking, and you can do your soft and hard freeze through CDP."
"CDD is primarily used for showing end users (managers, business teams, project managers, and release managers) what is happening with each release. The status and reporting features are very important. Automation reduces time to deploy. It also allows us to do more with releases and testing prior to production, better guaranteeing a smooth deployment."
"The most valuable feature for me is the fact that you can easily design a pipeline to promote applications from a development environment up to a production environment, and the team can become autonomous in designing those pipelines."
"Its ability to automate release deployments, streamline release scope, and reduce the cost of and time for deployment."
"Its extensive range of available connectors eliminates the need for manual code writing when implementing solutions, thus reducing coding efforts."
"The second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central."
"I like the fact that Ansible is agentless."
"Installing it is a PIP command. So, it's pretty easy. It is a one liner."
"The initial setup is straightforward."
"The biggest thing I liked about Ansible is the check mode so that we can verify, after we've pushed, that the config there is actually what we intended."
"One of the most valuable features is automation. We are doing automation infrastructure, which allows us to automate regular tasks. This solution provides us with a service catalog, like building new services and automating daily tasks."
"The API for exposing all our infrastructure services is the most valuable feature."
"I like being able to control multiple systems and push out updates quickly with just a couple of clicks of a button and commands. I like the automation because it is a time saver."
"It is agentless. I don't have to think about which client system my unit has understanding in or not, because I can execute from my system. It will go and configure it, and any module that it is looking for will be shipped out."
"Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more."
"CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition."
"We have rolled out the SAFe model, but what we would like to have is better integration with Agile Central, for instance, or at least at the plugin level, where we would select only certain stories instead of many stories in the sprint."
"The product's development has been stopped. It focuses on maintaining existing products."
"We would like to have a more user-friendly interface. It is already very friendly, but as soon as you start to have many applications with many tasks, the applications should be easier to manipulate on the screen."
"Reporting and dashboarding could be improved. Release pipelines should be creatable via templates as well as easily integrable/chained together. Visual navigation could also be improved when the pipelines become too large."
"Because Ansible is establishing SSH sessions to perform tasks, there is a limit on scalability."
"For Ansible Tower, there are three tiers with ten nodes. I would like them to expand those ten nodes to 20, because ten nodes is not enough to test on."
"The scalability of the solution has some shortcomings."
"Improvements should be made in terms of execution speed, which is, I believe, the most lacking feature. Aside from that, re-triggering a failed task is another useful feature."
"The tool should allow us to create infrastructure. It has everything when it comes to management, but it lacks the provisioning aspect."
"Networking needs to be improved."
"I have seen indications that the documentation needs improvement. They are providing a "How to Improve Your Documentation" presentation at this conference."
"Some of the Cisco modules could be expanded, which would be great, along with not having to do so much coding in the background to make it work."
More Automic Continuous Delivery Director Pricing and Cost Advice →
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
Automic Continuous Delivery Director is ranked 15th in Release Automation with 5 reviews while Red Hat Ansible Automation Platform is ranked 3rd in Release Automation with 58 reviews. Automic Continuous Delivery Director is rated 8.0, while Red Hat Ansible Automation Platform is rated 8.6. The top reviewer of Automic Continuous Delivery Director writes "An automation solution to automate the entire release process but lacks development". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Capable of broad integrations with easy-to-operate infrastructure and user controls". Automic Continuous Delivery Director is most compared with , whereas Red Hat Ansible Automation Platform is most compared with Red Hat Satellite, Microsoft Configuration Manager, VMware Aria Automation, Microsoft Azure DevOps and Microsoft Intune.
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.