Administrator at a recruiting/HR firm with 10,001+ employees
Real User
2018-06-28T11:31:00Z
Jun 28, 2018
We use a single application and are trying to deploy it with Automic Release Automation (ARA). It works for one component, so we decided to spread the tool to all our applications and make it the status quo. Today, we are still trying to deploy more applications with this tool.
Managing Partner at a tech services company with 11-50 employees
Real User
2018-06-28T06:32:00Z
Jun 28, 2018
This product has been chosen for automating application releases at a bank, who is our customer. The primary reason was to increase the patterns of releases from 12 a year to more. It performed really well. The pilot application that we implemented with them at the beginning of the year has been chosen to be a level up agile methodology, and within the three months that they used from the start of the project to going live, they have done approximately 600 deployments. This would have been impossible, given their present capacities.
Learn what your peers think about Automic Continuous Delivery Automation. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
Deliver apps at pace with agile development and let customer satisfaction soar.
Today, the pressure is on to transform how you deliver applications to market. Get release agility and speed without compromising quality and stability with CA Continuous Delivery Automation. Deliver apps reliably on demand from development through production—mobile to mainframe. Agilely scale as the cadence, volume and complexity of your apps grow. It’s DevOps-ready release management and automation for...
Our primary use case is for the deployment of web service applications.
We primarily use the solution for job run file transfers.
We use it to installing a complex application in a legacy world.
We use a single application and are trying to deploy it with Automic Release Automation (ARA). It works for one component, so we decided to spread the tool to all our applications and make it the status quo. Today, we are still trying to deploy more applications with this tool.
The primary use case is the implementation of software updates.
This product has been chosen for automating application releases at a bank, who is our customer. The primary reason was to increase the patterns of releases from 12 a year to more. It performed really well. The pilot application that we implemented with them at the beginning of the year has been chosen to be a level up agile methodology, and within the three months that they used from the start of the project to going live, they have done approximately 600 deployments. This would have been impossible, given their present capacities.
We deploy contained releases. This means we deploy every three months, nearly 160 applications, to our customers.