Please share with the community what you think needs improvement with Automic Continuous Delivery Director.
What are its weaknesses? What would you like to see changed in a future version?
What we would like to know is how to use CDD in Agile, at scale, in our organization. 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. We would like to have export capabilities to paper because, for auditing purposes, we need to keep them. We would like to add some documentation inside the tool as well. This is information we have already communicated to the development team of CDD and they will work on it. In addition, there is the testing aspect. It's a strong need now in the market: Not only to deploy/promote an application into whatever environment, but also to be able to execute testing and report on the quality of the application.
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.
CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition. If changed, we wouldn’t have two separate strategies for the tools since everything was in one tool. Both products could orchestrate and have overlapping capabilities. At the moment, we have to think about the strategy for each product. It would be great if CA RA and CDD were rolled into one product. CA RA is the “brains”, and CDD is the GUI/display.