The initial setup is very easy. Installation and configuration were very easy. Each time we configure, it's a similar process. Comparatively, the installation was easier than other tools.

It was straightforward. It implemented very quickly, it wasn’t an issue. No big issues.

The initial set up itself as relatively straightforward, what was a challenge was the roll out. You had competing priorities, you had adoption issues, you had skill set gaps. Not only on the roll out team, but on our development team. What we were able to do was close some of those skill set gaps. It became a journey where we had to show the value to each of the individual development groups, and it created momentum. As we got these development groups onto the CA release automation, they saw the benefit. We were able to take internal environments, and be able to turnaround those environments in seconds as opposed to days. We began to get the adoption. It's getting that initial movement forward which was really the challenge. I don't know that there's anything that CA could've done. It was something that we had to do internally.

The initial setup was very straightforward.

The initial setup of the tool itself was fairly straightforward. Setup of the individual application designs requires a comprehensive understanding of the application involved as well as getting everyone to agree on a standardized build and deployment process.

It was a very straightforward process. It took us a couple of weeks to set it up. I wasn’t involved in the process myself but was told by the technical team that it was easy.

I was involved in the initial setup. The product is very simple to setup. Because I'm part of the financial industry, the setup was very complex. From the product perspective, it is not very complex to set up. In my case, I needed lot of failovers and things like that, so my implementation was complex.

The initial setup was easy. We work with several environments and it doesn't take long move from the environment to one to the other.

We have problems with the CRT. We also deploy microservices. We have a lot of parameters that are different to go from one environment to another, and it's a lot of parameters that we have to deploy and change.

I was not involved in the initial setup of the different instances, directly. We had instances in the US, UK and Singapore. But I was involved in the consolidation or migration program when we migrated CA instances to one central server in a private cloud in Prague, Czech Republic.

It did not go smoothly. There was a lack of knowledge both at CA and within our team as well. We used a consultant who was not so experienced. He wasn't able to help us but when he escalated it on CA's side we got the help we needed. In the end, it was okay but it could have been much smoother.

For the setup, the complexity level was medium.

The solution's initial setup is quite complex. It's not straightforward.

Deployment took about two to three months for us.

The number of people you will need for your deployment depends on the project. In our case, we only needed two people to take care of it.

The initial setup was simple. However, if you want to use the tool in large installations, there are some tricks you should learn.

The initial setup can be open to more of the interpretation of the user. If you want to have it set up baseline, you just want to deploy out one or two types of products, that's pretty quick. It wouldn't take too much time. If you're trying to create it as a central enterprise solution for your company, then that's going to take a while. It took us about six months or so, maybe closer to eight, to actually get our real foundation set before we can quickly onboard and really automate adding artifacts to CA Release Automation.

Initial setup is a bit complex. We also had to build a front-end solution at the same time as implementing the CA and CDD. What we're doing with CDD is kind of unique. There's been some complexities. There's a lot of business rules surrounding the manual processes; getting all those captured; and then being able to program for them. Right now, we're looking at the 80%. Then we'll be going into an optimization come the beginning of 2017.

When it comes to agent install, it’s pretty straightforward. I can’t comment on the server installs.

I was not involved in the setup process but we were involved in product evaluation.

We work with CA's technology group for implementation. The setup was actually very straightforward. Because of the components we have involved, we're doing a lot of customizations to the product and then, again going back to scalability, allowed us to scale to those customizations.

Initial setup is pretty straightforward and we did not face any issues.

It is really straightforward to install and configure. However, it takes some days to fully understand how to properly use the tool due to the large number of features.

You need an expert to initialize the project. Initial setup of the product is simple as you follow a methodology. This is true for all products.

The installation was simple. But if you want to use the tool in large installations, there are some tricks you must know.

I've been part of certain POCs and the pilot. I think it was straightforward, not complex. But in some scenarios, it is complex. The level of complexity actually depends on which tool we are picking. On average, it is actually moderately complex.

It was a little complex.

We bought the product before CA purchased it.

This tool is complex, I recommend people design and develop a process with LISA RA who have expertise with shell scripting, and related tools such as SED, AWK, Perl, command line Unix or Linux definitely and maybe Java or POO basis.

With the help of a CA team, the initial setup was simple.

The initial setup is almost straightforward. The important thing is correctly sizing the architecture based on the number of agents to deploy.

The initial setup was straightforward. We did encounter a few issues, such infrastructure configuration, but I didn't think there was any major problems.

The initial setup was easy and straightforward.

It was complex in the beginning, and now its quite straightforward.

It was complex initially. The back end part was the main thing. Creating the action was done completely by CA guys. We just needed to know about the flow and the action. We wanted to learn about the action creation and development at the same time. But we took our time to learn those things.

It was already setup when I joined.

It's easy to setup and maintain afterwards.

It's moderately complex.

The installation was straightforward. Although we faced some problems, we realize that our flow could be improved.

Installation is straightforward and self-guided.

It was a very simple setup and easy to learn.

Initial setup was extremely complex due to infrastructure challenges and the specs required to get this implemented.

The initial CA RA setup is complex for getting you started but after you understand the way it distributes artifacts to its agent and the deployment phases, it then becomes quite easy to handle.

We were involved in the initial setup. We did the integration. We are also integrating this particular product with the other HPE products such as ALM, and so we are having our own challenges with that. We are working through those issues. Once complete automation is well done, it will definitely go to 10/10.

It ended a bit more complex than it should. The variables customization per environment formed a cluster of boxes, in the beginning, for instances.