Automic Continuous Delivery Automation OverviewUNIXBusinessApplicationPrice:
Automic Continuous Delivery Automation is the #8 ranked solution in our list of top Release Automation tools. It is most often compared to AutoSys Workload Automation: Automic Continuous Delivery Automation vs AutoSys Workload Automation
What is Automic Continuous Delivery Automation?
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 your dynamic enterprise.
Automic Continuous Delivery Automation is also known as CA Continuous Delivery Automation, Automic Release Automation, Automic ONE Automation, UC4 Automation Platform.
Download the Release Automation Buyer's Guide including reviews and more. Updated: September 2021
Automic Continuous Delivery Automation Customers
BET365, Charter Communications, TASC
Automic Continuous Delivery Automation Video
Filter Archived Reviews (More than two years old)
- Highest Rating
- Lowest Rating
- Review Length
Showingreviews based on the current filters.
Enterprise Architect at Spar BusIness Services
Jul 29, 2018
An umbrella system allowing us to integrate many different systems into our heterogeneous environment
Pros and Cons
- "It is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
- "It would be very beneficial for us to see integrations into cloud environments, especially into the Google Cloud environment because we are heading towards cloud."
What other advice do I have?I would rate the product as an eight out of 10.
Administrator at a tech services company with 10,001+ employees
Jul 16, 2018
The main benefit is you can deploy everything with it, but everybody has to need to use this tool in the organization
What is our primary use case?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.
Pros and Cons
- "The main benefit is you can deploy everything with it."
- "There is an issue with the stability in the tool. The process of agent will stop, then the monitoring agent can't be recognized because the process is running, but you can talk with the system."
- "If you have a technical problem and need development of the tool, the support team is terrible, because they cannot help with the technical details."
What other advice do I have?I would recommend not using ARA, but Automatic Workload Automation (AWA) because it is a more flexible tool. You can deploy and do release stuff on it.
Find out what your peers are saying about Broadcom, Red Hat, IBM and others in Release Automation. Updated: September 2021.
534,299 professionals have used our research since 2012.
Principal Project Engineer at a computer software company with 501-1,000 employees
Real UserTop 20
Jul 15, 2018
It can support very complex environments and dependencies
What is our primary use case?We use it to installing a complex application in a legacy world.
Pros and Cons
- "It can support very complex environments and dependencies."
- "It gives us good feedback on visualizations and on how our processes have progressed."
- "At the moment, the version that we are using (version 12.0), the environment is complex with multiple installations. Therefore, the monitoring is not scalable, but this should be improved in 12.1 and 12.2."
What other advice do I have?It is a good solution. It is very stable and supporting for legacy environments. For complex environments, which have to be installed or managed, then it is a perfect solution. We are at the starting point of our digital transformation and the speed up is just starting as everybody knows it is necessary. We can't stay with this manual installation, especially as the competition is not. Main criteria when selecting a vendor: A simple installation that they could use. They wanted a tool which could handle very complex environments with many dependencies and difficult workflows, but focus on…
IT Technician at a tech services company with 10,001+ employees
Jul 9, 2018
We can see which problems have been resolved from deployment
What is our primary use case?We deploy contained releases. This means we deploy every three months, nearly 160 applications, to our customers.
Pros and Cons
- "The most valuable feature is the ability to see which problems have been resolved from deployment."
- "We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
What other advice do I have?I would absolutely recommend this product.
Managing Partner at a tech services company with 11-50 employees
Jul 1, 2018
The product provides efficiency, in terms time, cost, and resources
What is our primary use case?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.
Pros and Cons
- "The product provides efficiency, in terms time, cost, and resources."
- "It provides a wonderful user interface which is easy to use."
- "Self-service for developers, because they are able to deploy to development departments on their own, without needing people from operations."
- "The dashboard should allow you to see the current state of packages in each environment, not only on an individual application basis, but across the entire application platform."
What other advice do I have?Get hands-on experience, because these solutions are very similar to each other on paper. Most important criteria when selecting a vendor: From the customer's perspective, the cost of tooling versus the productivity business benefit that it would bring in. Automic excels in this area, because it provides a wonderful user interface which is easy to use.
Project Manager at a transportation company
Jul 1, 2018
We increased our quality and reduced our time costs
What is our primary use case?The primary use case is the implementation of software updates.
How has it helped my organization?We save a lot of money. We have not had so many incidents in terms of correcting the deployment.
What is most valuable?We have saved on our time costs and have seen more quality.
For how long have I used the solution?One to three years.
What do I think about the stability of the solution?Stability is good. We have no problems.
What about the implementation team?CA Technologies technical support implemented the software. They were helpful.
What was our ROI?We increased our quality and reduced our time costs. In the beginning, we invested 50,000 Euro in the application. We expect the return to be more.
What other advice do I have?…
Architect at a energy/utilities company with 1,001-5,000 employees
Dec 31, 2017
Reduces our time to market considerably with automated and consistent results
What is our primary use case?We wanted to put in place release control, release management for our products, which is more centered around a COTS application, into an automated process. That's when we started looking for different tool sets and did a PoC with a couple of vendors. CA Automic stood out there. We started using it for both our service orchestration pieces as well as for release automation. So far, it's been doing well. In terms of our expectations, it's what we were looking for. There are some angles where we are still refining it or maturing our processes around it, but we have covered a lot in the last… more »
Pros and Cons
- "I would say our headwind, or our time to market, is reduced considerably. We get more consistent results out of it, because you write one time and once it's automated you expect it to behave the same way every time. And it cut down a lot of re-work for us."
- "The capability to provide visibility to the stakeholders, to management, is the biggest piece that showcases what the solution is about."
- "One of the biggest features I've been asked by my team to put in there is opening more scripting languages to be part of the platform. There is a little bit of a learning curve in learning how to code some of the workflows in Automic at this time. If widely used languages like Perl and Python were integrated, on top of what's already there, the proprietary language, it would make it easier to on-board new resources."
What other advice do I have?Our most important criteria when selecting a vendor are * the size of the vendor itself * how stable the company is * how long they have been in the market * what product suites they have that can help us achieve our goal at the end of the day. We look for partners, not vendors per se, that can help us implement our vision with us, and that's why we like Automic. I give it a good nine out of 10 at this time. The one piece that I think that could help leverage more of the tool is the scripting language barrier at this time. If that's not there, and some of the pieces that could be delivered…
DevOps Manager at a financial services firm with 5,001-10,000 employees
Dec 13, 2017
Gives us insight into the deployment process and metrics for evaluating it
What is our primary use case?Application deployment and orchestration. It has been performing very well for us.
Pros and Cons
- "Gives people insight into what's happening during the deployment."
- "The metrics gathered after deployment, for example, the rate of success versus the rate of failure."
- "I would like to see more support for WebSphere."
What other advice do I have?I would say, when you go to proof of concept, bring your next-to-the-worst-case scenario of what you need to get done; not the most complex but close to it. Because whatever you'll be able to hash out during the proof of concept, it positions you for better success when you actually decide to roll out.
Engineer at a financial services firm with 1,001-5,000 employees
Dec 7, 2017
Eliminates manual processes, reducing the risk of missing steps in the deployment
What is our primary use case?The key use cases will be eliminating manual activities, reducing the risk of missing steps in the deployment. The other thing is to speed up deployment, because the previous way of working was having someone to document the steps, someone to review the steps, and then at the end of the day, someone had to execute those steps within that window. So far, it has performed well, at least from the "repeatable" perspective. All deployments are repeatable, so when we have issues with deployment, it gives us the opportunity to review and to know where the issues came from. If it is working now and… more »
Pros and Cons
- "I think on a day-to-day basis, it has increased the capacity to deploy. We don't have to wait for someone to do something."
- "key thing is support for cloud-based deployment. That is lacking."
What other advice do I have?At this point in time we are not investing more because we already bought upfront. We are taking a wait-and-see attitude because, if the maturity of the platform plateaus, meaning we don't have new features, we might decide to move on. When we are looking for a new vendor, what is important to us is ease of migration. The other factor is the the currency of the platform, how current is it in terms of alignment to the market we are in. I give it an eight out of 10 because it does about 60-70 percent of the work. What it does, if it's done correctly, it does well. I would advise a colleague who…
DevOps Evangelist at a financial services firm with 1,001-5,000 employees
Aug 31, 2017
Enables easy creation of Action Packs for platforms where we are deploying artifacts and overall good UX
Pros and Cons
- "Deployment workflow (WF) can be designed this way, so that it is not necessary to provide all applications (systems) artifacts of which an application consists."
- "GUI for mobile phones: Availability to approve and start deployment through mobile phones."
What other advice do I have?This product is very strong and, on the other hand, very complex. So they should involve more technical people in the beginning to ensure knowledge transfer, and continuous and quick integrations of applications into this solution. The best option is to create a dedicated automation team before the implementation. The second important thing is that this solution provides only automated deployment and some orchestration as well, but deployment depends on all steps before, such as build and artifact preparation, testing, and provisioning. So others should use at least the automated build and…
Product CategoriesRelease Automation
Download our free Release Automation Report and find out what your peers are saying about Broadcom, Red Hat, IBM, and more!