The ability to manage frequent application updates across all phases of the application lifecycle — from development to QA to staging to production — is a critical test of an IT organization’s agility and alignment with business operations. Too often, deployments and handoffs are performed manually, raising the likelihood of errors and environmental inconsistencies. When server environments vary between development, QA, staging, and production, these differences frequently cause problems or outages when applications are promoted between environments.
Many organizations attempt to rely on manual tools or homegrown, script-based solutions to build and install release packages, configure target environments, and transfer releases among various environments out to production. These approaches are labor-intensive and error-prone, provide no security model to control who can “promote” code from one stage to another, and rely on staff to log all activity and, where necessary, roll back components. Image-driven deployment software for cloning and distributing application and system images does nothing to support the testing process that ensures the correctness of the original image. Neither of these approaches provide adequate granularity, adaptability, or validation of deployment processes and artifacts, all of which are necessary for successful application release management.
The BMC Solution
BMC Application Release Automation packages, promotes, installs, configures, validates, and selectively rolls back application deployments to reduce the time, cost, and risk associated with these deployments. It executes and tracks deployment steps — from build completion to retirement from production — across physical or cloud-based environments.
The solution automates the process of application updates, resulting in shortened release cycles, application configuration alignment, and automated updates across groups. Users can ensure that server and application configurations are consistent across environments by tracking application compliance in each environment against a distributed application policy model. In addtion, all deployment actions can be authorized based on user roles, ensuring appropriate levels of user access. If necessary, deployments can be easily rolled back, leaving environments in their pre-deployment state.