Nolio Release Automation Previous Solutions
I've worked on OpenShift, and I've also worked with IBM UrbanCode Deploy. In some aspects, Nolio is better than all those options.
However, as an administrator, there's a degree of uncertainty. I'm currently in a learning phase with Nolio, which I started using about eight months ago. At this point, I've become acquainted with around 70% of its features.
Nevertheless, I'm still unaware of the concealed functionalities that require exploration. Only after delving into these can I provide a more informed opinion.
View full review »Tools from other companies are more focused on Java implementations. We have a lot of off the shelf customers we have to work with, so at that time RA was able to do that. We had a lot of teams already doing work automating their deployments, so we looked for a cohesive approach. We were also deploying Secure Shell, so a mix of agents with Java and non-Java applications.
View full review »Our releases were getting bigger and bigger. The demand was getting larger and larger. We knew that the home grown tool was not going to be able to be scalable, basically. It was elongating our releases. We need to get our stuff done in a weekend, and it was beginning to drift into the following week. We went to the marketplace, CA Release Automation was a market leader, we made a quick decision in that direction. We haven't regretted it.
The support we've had with CA in the past had been very strong, those were important to us. Then, the depth of the solution. I think we're looking into the depth of the solution, and the agility and flexibility of that solution, I think were important to us in this decision. We're with a large player, somebody that could support us if we needed. The tool, from everything we had been reading and researching, it could stand up to it. I think those were the things that we were looking for.
Buyer's Guide
Release Automation
March 2024
Find out what your peers are saying about Broadcom, IBM, Digital.ai and others in Release Automation. Updated: March 2024.
765,386 professionals have used our research since 2012.
We bought two solutions together. One is Release Automation, because our release planning team had a very strong gating process. We have to go through a approval process. They have a very strict change management process. The release automation tool did not fit really well into the process, that's why we need to go for another solution.
Our application portfolio is growing and our release window is doubled but our customers start complaining, okay when you do release software, we have to take our production system down. We want a tool to move core faster so we can bring down our release window and take a very brief outage in the production.
View full review »In terms of actually implementing the tool technically, it's straightforward. The challenge that we've got within our company at the moment is that we're in the process of trying to roll out a cloud. It's trying to understand how Release Automation fits with that because I think it's getting very on-premise focused until now. And that's one of the challenges that we've got.
View full review »We used legacy UNIX deployment scripts to perform automated deployments through CLI. Maintaining the scripts was a tremendous overhead for the release operations team. These scripts had to be regularly updated to ensure that they can deploy the latest and greatest technologies to which the company was switching.
View full review »We used several different solutions to achieve similar results. One of the biggest advantages for us in choosing this solution was the ability to incorporate, build, deploy, and test functionality in a single pane of glass.
View full review »We didn't really use any other solution before. We were using a manual operation which was extremely intensive. Thus, the daily pain involved and the money that we were spending on it were the main reasons for us to lookout for another solution. Money and the time we spent were the biggest variables involved.
For us, it was important as to how quickly we could get started and how much the vendor was willing to invest in us. CA was willing to invest in us as much as we were willing to invest in them; that made the difference.
View full review »We were trying out many different solutions and CA RA was one of them.
View full review »RV
Rahul Verma
CA Lisa Developer at a tech services company with 1,001-5,000 employees
We didn't previously use a different tool.
View full review »MC
reviewer211584
SQA Manager at a tech services company
I use open source solutions like Puppet and Chef. These solutions require a high level of expertise and are difficult to maintain in large installations. For this kind of project, it is better to use commercial tools like CA Release Automation.
View full review »We decided to invest in CA Release Automation because we were trying to find ways to be more efficient in our code delivery. We had a lot of outages surrounding releases going wrong, and part of that is also code not being built automated; versions not being the same from QA to production; just a lot of those little things that built up over time.
We also expanded as a company, so we finally have started looking at everything that we can fix and this is one of the places that we started with.
When we work with vendors, I would say just being able to actually be listened to is something we look for; whenever we have issues, actually getting responses from the companies. I find that CA actually will respond. They might not have everything out of the box that we want, but they'll listen, and they'll actually update their code and add more plug-ins. One thing that they have actually updated; we requested TIBCO version 6 for BW deployments to be added as a plugin, and they're in the process of actually adding that to their new release, on the roadmap.
View full review »My organization has wanted to invest in a solution for my group for a couple of years now. It was a matter of just researching, getting the right players in, and bringing in the right development people to start on this. I started on this process about two years ago. We finally got the team set up so that we could move forward on it at the end of 2015. Then we started full blast ahead in January 2016.
View full review »Unfortunately, all we used for deployments previously was custom scripts, so I can’t compare here anything.
View full review »We were not using any other product prior to this one. We were carrying out the entire process manually.
View full review »EchoStar actually has CA Technologies Release Automation implemented in another team, so we're partnered with the other team. We looked at the product in comparison to building custom applications ourselves and found that using CA technology was the best solution.
What I look for from a vendor is somebody with the technical skills that has the knowledge of the best solutions, best practices; and that has a support team that we can draw on, call on, and that we can then use as mentors as we bring our team up to speed.
View full review »I had used IBM RAF for deployments. It does not have the same flexibility as CA Release Automation for automation in it.
View full review »We previously used a different solution.
CA Release Automation really makes life easier as follows:
- Has a large number of available actions.
- Has deployment pipeline and approval gateway features that increase security to the deployment flow.
- Integrates with service desk tools.
I switched from CA Release Automation (Nolio) to Serena Release Automation one time because Nolio was a partner of Serena. When Nolio was bought by CA Technologies, the partnership was broken so Serena advised the client to migrate to a new tool (UrbanCode).
View full review »MC
reviewer211584
SQA Manager at a tech services company
I used open source solutions like Puppet and Chef. These solutions require a high level of expertise and are difficult to maintain in large installations. For this kind of project, it is better to use commercial tools, such as CA products.
View full review »Originally, there was no solution. Then there was a solution, but it was in small cell buckets. Now the solutions are getting integrated together.
View full review »No solution in place, and we were doing everything manually.
View full review »We had no previous solution.
View full review »We used to do the deployment manually, which lasted for hours, and it didn't usually work in one go. So to automate the deployments we started using Release Automation.
View full review »NV
Nikhil Vyas
Software Build & Release Architect/ DevOps at HMS
We were using an in-house developed release tool, but wanted better orchestration for our releases.
View full review »We used a home-grown product on the IBM side. We wanted to enable faster continuous integration dev-ops methodology.
View full review »I am not 100% certain because I wasn't involved in the beginning. I think as I mentioned earlier, we were using Shell Scripting for deployment and we needed a level of expertise in scripting to understand those scripts and make changes in it. The other reason was that the support team can focus on operational support rather than live deployments.
View full review »We had always used an in-house tool.
View full review »No previous solution used.
View full review »I haven't used a different solution.
View full review »No previous solution was used.
View full review »No previous solution used.
View full review »I used Numara Software by BMC, but it wasn't a switch, though; it only was another customer.
View full review »LG
Lidor Gerstel
DevOps Engineer at a comms service provider with 501-1,000 employees
I used Puppet Labs as a configuration management tool and compared it to CA Release Automation. The products are completely different in features, functions and methodology.
View full review »I worked as a consultant, so we had very different tools applied. It all depended on the client itself.
View full review »Buyer's Guide
Release Automation
March 2024
Find out what your peers are saying about Broadcom, IBM, Digital.ai and others in Release Automation. Updated: March 2024.
765,386 professionals have used our research since 2012.