We didn’t have a previous solution. We just had a very wide variety of custom in-house scripts.

We were previously using a home-grown solution. That solution couldn't scale, was risky to make changes to, and could not provide the features we need to achieve continuous delivery.

We were completely manual before this.

Management wants to use UrbanCode to make sure that we all deploy the same way. I do not know if they evaluated other products. I was just given the product at the moment and I was in the company already for some time. The strategy behind this is that everybody deploys with UrbanCode.

We weren't using anything before and we had to get something up and running quickly. It did take us a little longer to get the uDeploy up and running than we'd hoped, but once we did it certainly met all of our needs.

Before UrbanCode was implemented in the organization, we used to perform the basics using Jenkins. However, it was a very lengthy and difficult process.

For some of our products, we are not using UrbanCode. For example, we have implemented Ansible and we are looking forward to using it more as a Linux tool. The major difference between the two is that Ansible is agentless. I just need to log in to the server and do my deployments. The issue we are having with UrbanCode, where we want to keep the agent up and running at all times, is automatically resolved using Ansible.

We will continue to use multiple products for the time being.

We did not previously use a different solution.

Our existing solution was mostly manual deployments so that, of course, is very error-prone. We looked at several different solutions to try to see what we could implement quickly and what would have the most impact, the most return on investment in a relatively quick amount of time. This was the tool we decided to try out and so far it's working pretty good.

The prior solution was created by our company. We determined that to add the features required to expand our solution, it was better to use a vendor product.

Yes, we used Build Forge. It's a build tool that was being re-purposed for deploy and it was beginning to fail often.

We didn’t have a previous solution. This was our first real attempt to introduce one central deployment tool to automate and standardize deployment processes for all techniques, such as Linux, IIB, IIS, and WebSphere.

We chose the product because we have a long-lasting relationship with IBM.

We previously used IBM Rational Build Forge and then migrated to UrbanCode Deploy, which has more flexibility and process-oriented features.

The previous solution was a mix of manually copying files around and logging into systems to run scripts. IBM UrbanCode Deploy enabled us to easily take builds from SonaType Nexus and deploy them into the environments without needing manual steps.

No.

We had home-grown solutions different for different applications. We have standardized by adopting this solution.

We used BMC BladeLogic previously. BladeLogic is more for automating tasks performed on servers like compliance, patching, and provisioning. It is not suited for devops/application deployment and hence the migration from BMC to IBM.

We had various solutions before this one.

Yes, I have used FinalBuilder for deployment automation - which did not use a Server/Agent model or offer any sort of repository management or inventory tracking, which were the major selling points for Urbancode Deploy.