The setup is very easy so I rate it an eight out of ten. 

The setup was quite easy. We are still in the process of rolling out the solution to the entire organization. We are still using Automic for infrastructure configuration management. We offer our development teams multiple options including UCD and Jenkins however, UrbanClode Deploy is our main choice.  

Initial setup was straightforward.

Initial setup was complex. There is a lot to consider in a large enterprise: security model, resource tree strategies, infrastructure topology (UCD servers, agent relays), management of UCD agents (installation, monitoring, troubleshooting, etc.).

Initial setup was complex, as providing user privileges, environment-application mapping, and environment release allocation are some of the pre-install tasks to be completed for creating a plan. Creating a long plan is also complex.

I set it up, but I did have someone bless the configuration to reassure us that we had set it up well enough to scale to cover our IT.

It was complex at times. It took us a while to come up with the standard process that we needed, but then once we had it it also took a while to actually get all of our projects up and running. We didn't know how to use the CLI at that time. We might have been able to do better if we knew that.

The initial setup is easy, although it depends on the tool that you are comparing it to. For example, Ansible is a similar tool that is not agent-based. Overall, I would rate the ease of setup a three out of five.

I was not involved in the initial setup & configuration.

It's very time consuming, the setup of the solution. We ended up scripting a lot of it, so that it was quicker. There's a lot of pieces that you have to set up for one particular job to run on it. You can actually make steps and end up having to sit there and figure out what you missed, so we ended up scripting a lot of it so that we wouldn't miss pieces, which made it also quicker to set up new applications, to be able to get all the way through deployment.

The initial setup was straightforward and well-documented.

Very straightforward. Command line prompts to install all components, and hook into enterpriseDB. Trial version will use its own Derby DB.

The initial setup is easy and straightforward.

Initial setup was done on only one environment. Even then, UCD has a quite complex setup due to a needed high-available setup with load balancers, queue managers, license servers, and databases.

Depending on the size and complexity of the organization, you need at least three environments:

• To develop and test new versions of UCD
• To build reusable deployment solutions
• To execute them

The initial setup was pretty straightforward with the installation of agents and clients. The configuration process and specific jobs are dependent on the complexity of your application or project.

The initial setup was straightforward. It was very easy to install and configure IBM UrbanCode Deploy and remotely deploy its agents.

Initial setup was not that complex, but you need to work on integrating this with your company standards, and tools and policies supported.

It was fairly simple as the product is easy to install.

Setup was complex because IBM started on the wrong foot.

Initial setup in a clean environment is very straightforward.

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

Deployment times vary. It took us between five to six hours.