The tool has been quite stable. Once we configure it properly, it remains very stable. For general use cases, it is a very stable tool. 

However, it is still difficult for beginners to configure the Nolio. 

We push the edges of the tool, so we have a lot of stability issues on a daily basis. The database interface, the users who access that data – when it goes down it affects a lot of clients. It impacts a lot of applications once it breaks up.

There are misinterpretations of data between an application if it’s written in a certain way, fit to use with different databases for examples with the hibernate layer, the layer can wrongly execute.

The RA product itself is able to produce queries which you can easily program, but which translate into taking a huge amount of memory which is not available in a server. If you’re in an ROC you see an overview of all your deployments, maybe 25-50 deployments with the query underneath, which queries everything that hasn’t been run. For several hundred applications that translates into huge overhead and performance problems. We’re working very closely with CA to address these problems.

Very stable. We were fortunate that early on, one of our internal technicians/architects sat down with CA. Went through the process of designing what the solution should look like. We're benefiting from that up front set up and structure of the tool in order to make it very reliable. It's enterprise wide, it's being used by all groups.

The product is very stable. We had minor performance issues but we contacted CS Support. They gave us a solution to fix the issue.

We haven't actually got as far as configuring the Production Instance. We've only dabbled in the POC. So it's hard to tell at this time.

We did have stability issues. The tool slows down often. If any agents were to go offline or are in a hung state, we do not discover this until after the deployment has been triggered. The workaround for this is to leverage a third-party monitoring tool to ensure that it polls the agents 24/7 and takes the necessary configured action if the agent were to have any issues.

There were no issues with stability.

So far, it has been very stable. We have been using it for 2 years and have had no issues. We have experienced some minor issues but nothing major.

The product has evolved a lot. I started my journey with Version 4.7 and now they have come up with Version 6.1. I'm seeing the product becoming more robust. I'm sure CA will make it even more robust in the coming years.

It is stable.

It's pretty stable.

We did have some stability issues. Sometimes, my agents on the deployment servers failed to connect with the CA RA server. So, I had to restart the agents on deployment servers once a week in order to make them active again on the CA RA admin console.

The solution is quite stable. We haven't faced any bugs or glitches or noticed anything at all that has affected its performance.

We encountered a stability issue, but it will be solved with the collaboration of the CA teams.

The solution itself is pretty stable, as long as you're integrating it with enterprise solutions, as well, using an enterprise database, because it's a pretty database-intense product. Don't try to use some sort of MySQL. Use something that's real, as well as the repository for your artifacts, using an enterprise Nexus or enterprise Artifactory, instead of just the built-in products.

I believe it will be stable. We're still finishing up some introductory things. We haven't done our full release yet. We're in a soft test process right now. I'm starting to see some very positive results with all of that.

I have not encountered any particular issues, as all I had to do is the agent software installation and configuration. The vendor and a supporting team installed the system servers.

It is good and is doing what it is supposed to do. I don't see any challenges. After observing the success rate for deployment, we are getting more participation from different applications; so, it is doing good as expected.

What we actually did is, we took our software and moved it to another location that makes it incorporated into our infrastructure up at the up-link center. By doing that, the stability of the solution allows us to be able to do more real-time work, rather than trying to have to do manual entry.

Yes, stability is a persistent issue for us. We spend an average of 1 - 2 hours a week troubleshooting offline agents. I am told that a lot of these issues have been addressed in the 6.2 version that is now available and we are in the process of upgrading.

The tool is very stable and any issues we have encountered have been due to infrastructure-related issues (servers/VMs) or human error.

The product is pretty stable.

Never had any stability issues.

There have been stability issues, but they will be solved with the collaboration of CA teams.

Whenever we pick a new solution and we try to install it, there are some hiccups in the initial stage. Once that is done, I think the issues are small.

No issues encountered.

We've had a few outages due to bugs. We were able to work around the bugs, but it was a frustrating process.

No we didn't have any stability issues, everything is OK.

If more than 150 nodes are connected to the execution/NAC server, then we observe slowness in the execution of the processes. This then leads to time-outs, and the deployment fails on some of the nodes.

The product was very stable and reliable. This was also the case in big installations with a lot of agents involved, thanks to the high availability architecture.

I believe it's pretty stable. Of course, there are chances of improvement in any tool or any application. But CA Release Automation is a pretty stable application where one core piece can communicate to multiple sources and targets, which I love personally.

It was in the development environment, but we didn't see anything.

Yes, we have had some issue because we migrated a product database from a normal Oracle environment to an Oracle RAC cluster environment. This has affected the performance for some time.

It's stable but there are few updates we need to do because of the new changes. We need to add more actions items, because we were using one tool, and we were deploying the application, so we needed to make sure that that the configuration tool can be used with the help of RA.

We use two versions – the older version (4.4) is very unstable, while the newer one (5.5) is much better. So we went from many issues to far less.

No issues with stability.

Yes, every version had some bugs, which are reported back to CA and are accepted and fixed.

There are some stability issues. Sometimes, the server crashes or throws out of memory. And the import/export function sometimes doesn’t work.

Once in a while, the agent gets into a frenzy, and an agent restart is required.

Yes, because of the bugs with the action packs.

It was reliable.

We encountered no stability issues.