IBM DevOps Deploy vs. Webapp.io

IBM UrbanCode Deploy is excellent for code deployments such as Java, .Net, C++, etc. It can also deploy and run SQLs reasonably well. Where it lacks is the ability for executables, Jars, WARs, EARs, etc.

Incentivized

• Consistently deploys to multiple environments with no changes to the process. Having reusable processes across environments from Dev to Production make deployments more consistent and easier to manage.
• IBM UrbanCode Deploy has an easy to understand UI, to be able to review if a deployment has successfully completed or not, and details if it did not work. Using the UI is simple and easy to understand.
• Scheduling and approvals are built-in as configured for the deployments. This allows us to use the same deployment process, but get approvals as needed when code is moved up to the upper environments.

Incentivized

• Use of the internal API for public API use.
• Less cryptic CLI output on commands.
• Better use of custom variables that don't interfere with UCD's use.

Incentivized

It's challenging to get a working knowledge of the product without having someone show you the ropes. Linking components with applications and applications with resource trees and resource trees with application deploys is not intuitive. However, once past that learning curve, the possibilities open up, and things become easier to understand and allow for further granularity.

Incentivized

I've not worked directly with IBM UrbanCode Deploy support. My DevOps team administers the environment and deals with that.

Incentivized

• Push button deployments.
• Consistency and ability to focus on other tasks.
• Required quite a bit of upfront customization with certain web deployments (WebSphere, etc.)
• Opened the door to other types of deployments and other automation.

Incentivized