Automic Continuous Delivery Director Pros and Cons
Automic Continuous Delivery Director Pros
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.
The second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central.View full review »
Its ability to automate release deployments, streamline release scope, and reduce the cost of and time for deployment.
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.View full review »
Automic Continuous Delivery Director Cons
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.
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.View full review »
CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition.View full review »
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.View full review »