It has been a key enabler for us to implement Continuous Delivery and DevOps across the organisation. We have been able to increase release frequency with a factor of (approximately) 10 and reduced re-deployments with a factor of 50!

Visualizing the DevOps progress

Unlike other colleagues, I'm able to speed up the delivering process. I use DeployIT with WebLogic and Tomcat servers. Everything is fine set up just in two minutes. Even in 2014, we can easily find people who copy manually their own packages directly to production environment! It's completely incredible.

No more need to write a 40-page handbook to perform a deployment.

For our organization, the speed of deployment is paramount. The speed at which we can deploy is enhanced by automation with this product and has been much faster than anything else we experimented with.

If you ever write a lot of deployment scripts and playbooks, et cetera, and you have to maintain all of this it becomes a burden. In this case, we didn't have to do as much of that maintenance. First of all, as an example, say somebody writes a script and he leaves your company in a year's time. Then somebody else looks at that script and the guy who wrote it came at it from a certain perspective and it may not be easy to interpret. It works for some cases, but in other cases, it isn't quite right. You don't exactly know what cases it was written for or what other scripts it had to be used with. There's lost knowledge of the purpose of the script because the person who wrote it is gone.

Instead, with XL Deploy this is scalable because you define your deployment package using your favourite CI tools, and you point it to a logical application-centric environment to which it needs to deployed. The rest of how it needs to get deployed and based your specified deployment pattern like blue-green, canary etc, the deployment plan  is generated by XLDeploy and the application is deployed.

We don't really spend time building scripts and maintaining scripts as part of something someone has to remember any more. XL Deploy does that for us and the deployment knowledge does not get lost. So, you actually accelerate processes of deployment and automation is much faster than with other platforms.

We don't feel the learning curve for XL Deploy is very high. For the company, this means you don't necessarily need the same level of specialist skills for a successful deployment. It is much easier for people who are new to it to learn how to use it. That has become a big element for us pushing ahead, and it has made a serious impact on the way we apply scripts and deploy applications.

For a "from scratch" project, the build pipeline is very easy to create : Jenkins for the continuous integration platform and deployIt for "push" the artefact onto our servers.

Simplification of the pre-production and production installation.

Jenkins deployment was hard to maintain different environments, different variables, Machines etc. Now we have it all under one roof.

Shorter time to market, more agile in deploying newly created business value.

Quicker and more solid installations.