We performed a comparison between Automic Continuous Delivery Director and Microsoft Azure DevOps based on real PeerSpot user reviews.
Find out in this report how the two Release Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"Its ability to automate release deployments, streamline release scope, and reduce the cost of and time for deployment."
"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."
"The second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central."
"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 extensive range of available connectors eliminates the need for manual code writing when implementing solutions, thus reducing coding efforts."
"The initial setup is very easy."
"My first impression of DevOps, after using Jira, is that it has a much better, more intuitive, and more user-friendly interface."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"The creation of test plans is valuable and I like the reporting features."
"The solution is scalable."
"Everything that's related to the pipeline has been very good."
"The tool's most efficient feature is the integration of its services in one place. It is an easy-to-use product that improves productivity. Microsoft Azure DevOps is also user-friendly. Its documentation is clear and can be found on Google."
"Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development."
"CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition."
"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."
"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."
"Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more."
"There are some areas that need improvement such as tracking."
"Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult."
"It should be easier to manage Licenses especially because it's in the cloud."
"It would be great if I could integrate with a human resource type of software that could control timesheets."
"One thing I would note is that it's hard to know what is included or not in the product. Especially when you begin to try and compare it to other solutions. When you go to a site like VersionOne, they tell you Azure DevOps doesn't have this or that, and when you go to Microsoft, it says VersionOne doesn't have this or that. They could do a better job of laying out exactly what is on offer so customers know going in exactly what they'll get."
"Something that could be improved is the initial setup with the integration of ReadyAPI."
"As for room for improvement, more features need to be added to the classic pipeline. The build and release pipelines are present, but there has not been much improvement there."
"Improving the metrics that are readily available on the dashboard would be very helpful."
More Automic Continuous Delivery Director Pricing and Cost Advice →
Automic Continuous Delivery Director is ranked 14th in Release Automation with 5 reviews while Microsoft Azure DevOps is ranked 1st in Release Automation with 127 reviews. Automic Continuous Delivery Director is rated 8.0, while Microsoft Azure DevOps is rated 8.2. 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 Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". Automic Continuous Delivery Director is most compared with , whereas Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and ServiceNow Strategic Portfolio Management. See our Automic Continuous Delivery Director vs. Microsoft Azure DevOps report.
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.
