Deployment Automation vs. Release Management Automation

in a previous blog, i compared deployment automation to build automation . i wrote about the differences between the build and the deployment process and i explained why different features are required from the respective automation tools. in this blog i will explain the difference between release management and deployment and why release management tools that claim they do deployment automation are actually doing something different. and why that is a good thing.

let's start by defining release management. while wikipedia might define release management as a relatively new discipline in the application lifecycle management space, it has actually been a part of itil v2 since its release in 2000. it concerns itself with the management of software releases. courtesy of the itil open guide , the key activities of release management are:

1. conduct release planning
2. coordinate design, building and configuring of releases
3. coordinate release acceptance
4. conduct rollout planning
5. coordinate release communications, preparations and training activities
6. coordinate distribution and installation of releases
7. provide management information about release management quality and operations

as you can see, release management is very much about managing the software releases, not about the actual work involved. activity #6 is only the management of the actual deployment! as my colleague robert van loghem has described in his blog so what is a deployment really? , the key activities of deployment are:

• installing applications
• configuring installed applications for the target environment (test/acceptance/production)
• configuring resources
• configuring middleware components
• starting/stopping/restarting server and applications

not only are the activities different, different people are responsible. while, depending upon the organization, a release manager or project manager is responsible for the release management process, the actual deployment will be carried out by a system or application administrator.

because application deployment is a complex process which tends to be unreliable and costly if handled manually, there is more and more pressure on companies to look at deployment automation product such as deployit . that also explains why release management tools such as thoughtworks go and rational build forge are now being marketed as supporting deployment. but if you look closer at what they actually support, it boils down to just invoking a deployment script. and that is not what deployment automation is really about. it's about installing applications, configuring resources and restarting servers!

but this is not necessarily a bad thing: i would also not expect a release management system to include a build automation system because a release manager is not responsible for actually building the source code. i'd rather use ant , maven , or gradle . in a similar vein, i'd rather have the release management system invoke a proper deployment automation system to perform the actual deployment.

that way, each tool can focus on the process it wants to support and provide the right feature set for the right target group. release management system for release managers, build systems for developers, and deployment automation systems for system and application administrators.

from http://blog.xebia.com/2010/11/25/deployment-automation-vs-release-management-automation/