UrbanCode Deploy Review

It has flexible deployment options, allowing us to model our components as we want and need. More plugins are required.


Valuable Features

It has flexible deployment options, allowing us to model our components as we want and need, which is the most valuable feature we've found from our experience with it.

Improvements to My Organization

It reduced more than 70% of our manual effort when it automated deployment of both UNIX and Windows-based applications using UrbanCode Deploy. We used plugins available in the plugin center and used UNIX shell and powershell scripts to automate completely.

Room for Improvement

More plugins are required. There are also many bugs in UrbanCode Deploy. Finally, database deployment and rollback of databases needs to be worked on.

Use of Solution

I've used it for one year two months.

Deployment Issues

It does not support variable changes and utilizations while executing the application. We were setting the variable values in the application process and using it in the same process, but apparently that's not supported.

Stability Issues

There have been no issues with the stability.

Scalability Issues

We have had no issues scaling it.

Customer Service and Technical Support

Technical support is very good.

Initial Setup

Refer to the IBM Learning Center as that will help with the setup

Implementation Team

We used a vendor team for our implementation.

Other Solutions Considered

Rundeck is also a good option, but UrbanCode Deploy provides more features and is easier to use.

Other Advice

Before buying this, try the trial version and check if it serves your purpose.

Disclosure: My company has a business relationship with this vendor other than being a customer: We're partners.
1 visitor found this review helpful
1 Comment
Eric MinickVendor

Thanks for the feedback. Would love to know what plugins you are looking for. And for dynamically setting values during a process, look at capturing dynamic values as the output properties of one step and referring to them from another. That's a "chalk board" you can write to in flight. The app properties are not because each deployment uses a traceable version of the props for audit / repeatability purposes. When the process updates those properties it is creating a new, different version of the props. So I'm guessing you can get the dynamism you're looking for with a different approach.

Eminick@us.ibm.com

15 June 16
Guest
Sign Up with Email