DevOps Engineer at a insurance company with 5,001-10,000 employees
Real User
Nov 7, 2022
The solution is a great tool for hands-on deployment that is straightforward. It is easy to get exposure in terms of real-time work. I recommend the solution and rate it an eight out of ten.
Software Engineering Director at a transportation company with 10,001+ employees
Real User
Jan 4, 2022
Trial and error is the best way to determine if this solution meets specific needs. This is a good solution for enterprise-level deployment automation. However, it may not be the best solution if one is only looking for a simple solution for deployment automation. We are currently comparing this solution with other options in the market such as Azure pipelines or the GitHub actions. I would rate it a nine out of 10.
Professional Services Leader at a tech services company with 11-50 employees
Real User
Oct 22, 2020
If you are deploying independent components that are not involved in an enterprise scenario, then maybe this solution could work; however, if you have a complex scenario with multiple components and multiple complications, then it's better to choose a more powerful solution. On a scale from one to ten, I would give this solution a rating of ten.
Software Engineer at a tech company with 10,001+ employees
Real User
Feb 16, 2020
This is a solution that I recommend but I think that for anybody who is interested in implementing it, I would suggest that they start by reviewing the resources that IBM has online. It is not complicated, and they will be comfortable with how the variables are used and that kind of thing. I would rate this solution a seven out of ten.
Rollout Manager at a transportation company with 1,001-5,000 employees
Real User
Mar 6, 2019
In my opinion, the way you have to develop with UrbanCode Deploy is to use the graphical interface, which is nice. However, for development UrbanCode Deploy is slow. Each time you have to click on something, you have dropdown menus, etc. I am a coder by nature. Some tasks I would normally prefer to go faster. It would be better if I could type commands directly using UrbanCode Deploy. I would give UrbanCode Deploy a six or a seven because it is not easy to set up. The documentation is not commonly found. I think it's pretty expensive too. UrbanCode Deploy is not so much used in the market. When you implement, it's not so easy but you can overcome that. Afterward, when it runs, it runs slowly to complete. Now that we have the solution, we rely on it and really trust it now. I would have given it more points if it were easier to work with. My final rating would be seven out of ten. Take at least one month and properly evaluate the tool with a real business case because it was sold to us in a different way. We were told this tool can do anything and within a week you will have a solution. In reality, it took us three or four months even to come to the final solution. The tool is not as easy as the vendor says it is. You have to get used to it and you should not think that this tool is just magic that will solve your problem. You have to think around your current problem and then see how you can get that into the tool and not vice versa. Don't expect the tool to solve your problems.
UrbanCode Deploy offers a reliable solution for deployment automation, enhancing application delivery with features like Server/Agent architecture and visual process design, ideal for efficient deployment across environments. UrbanCode Deploy is crucial for automating deployments and managing containers and Kubernetes. It connects applications, manages artifacts, and supports standard, blue-green, and complex deployments for development to production pipelines. It enables efficient...
The solution is a great tool for hands-on deployment that is straightforward. It is easy to get exposure in terms of real-time work. I recommend the solution and rate it an eight out of ten.
Trial and error is the best way to determine if this solution meets specific needs. This is a good solution for enterprise-level deployment automation. However, it may not be the best solution if one is only looking for a simple solution for deployment automation. We are currently comparing this solution with other options in the market such as Azure pipelines or the GitHub actions. I would rate it a nine out of 10.
If you are deploying independent components that are not involved in an enterprise scenario, then maybe this solution could work; however, if you have a complex scenario with multiple components and multiple complications, then it's better to choose a more powerful solution. On a scale from one to ten, I would give this solution a rating of ten.
This is a solution that I recommend but I think that for anybody who is interested in implementing it, I would suggest that they start by reviewing the resources that IBM has online. It is not complicated, and they will be comfortable with how the variables are used and that kind of thing. I would rate this solution a seven out of ten.
In my opinion, the way you have to develop with UrbanCode Deploy is to use the graphical interface, which is nice. However, for development UrbanCode Deploy is slow. Each time you have to click on something, you have dropdown menus, etc. I am a coder by nature. Some tasks I would normally prefer to go faster. It would be better if I could type commands directly using UrbanCode Deploy. I would give UrbanCode Deploy a six or a seven because it is not easy to set up. The documentation is not commonly found. I think it's pretty expensive too. UrbanCode Deploy is not so much used in the market. When you implement, it's not so easy but you can overcome that. Afterward, when it runs, it runs slowly to complete. Now that we have the solution, we rely on it and really trust it now. I would have given it more points if it were easier to work with. My final rating would be seven out of ten. Take at least one month and properly evaluate the tool with a real business case because it was sold to us in a different way. We were told this tool can do anything and within a week you will have a solution. In reality, it took us three or four months even to come to the final solution. The tool is not as easy as the vendor says it is. You have to get used to it and you should not think that this tool is just magic that will solve your problem. You have to think around your current problem and then see how you can get that into the tool and not vice versa. Don't expect the tool to solve your problems.