We performed a comparison between Automic Continuous Delivery Director and Microsoft Azure DevOps 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 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."
"The second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central."
"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."
"Its extensive range of available connectors eliminates the need for manual code writing when implementing solutions, thus reducing coding efforts."
"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."
"Most developers and project managers choose the Microsoft tools to begin with because of familiarity, and these new tools are almost an extension of the tools you're already familiar with. There's a lot of knowledge transfer, which helps, rather than bringing in a new product line."
"What I like most about Azure DevOps is how easy it is to manage projects and control deployments."
"The most valuable feature is that it brings order to our projects, and we know the status of each one at every moment."
"The nice thing about Visual Studio Code is that it's a modular design. So if you're working on a strange language that has a different syntax, you can just get a plugin that'll format your code for you based on the language it's in."
"It is easy to use. The shared repository is useful. Everything is in one environment."
"We are able to generate many different types of reports from Azure."
"The simplicity and ease of use are two features that we have found to be most valuable."
"The most valuable feature is the complete integration between test cases, pipelines, and issue management."
"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."
"Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more."
"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."
"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."
"It is very difficult to integrate the product with third-party tools."
"Another area is the Azure monitoring agent for Citrix machines. There's room for improvement there too."
"There are certain areas in Azure DevOps that are better in other products."
"Compared to JIRA, I think Azure DevOps is missing some management elements, like some reporting features. It would be helpful if some things were clearer when we're adding attributes. For instance, sometimes we want to add some categories or attributes, and it's not so easy."
"With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem."
"When we don't have some permissions, we have to research how to get them."
"Integration and plugins for other tools could better. Like if you want to integrate the DevOps with other tools that are in the market. This could be for the engineering tools to check code quality, application security tools, and DevOps dashboard tools."
"Azure DevOps is set up more for development and less for testing. If it is set up correctly, everyone can use it better, but it was set up from a development point of view, which means it is lacking in what I need from a testing perspective. Just like any other tool, it depends on how it is configured. I am not happy with the way it is set up. It is configured more from a development side, and it doesn't necessarily cater to all the other areas that probably need to use it, such as testing data, etc."
More Automic Continuous Delivery Director Pricing and Cost Advice →
Automic Continuous Delivery Director is ranked 15th in Release Automation with 5 reviews while Microsoft Azure DevOps is ranked 1st in Release Automation with 123 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 "Good support, helpful management capabilities, and great Kanban boards". 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 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.