Scenario 1: DevOps

Breaking down silos with automation and visibility

DevOps is characterized by better collaboration across functional groups, especially between development and operations. With IBM UrbanCode Deploy developers and production support teams can use the same automation to deliver changes throughout the lifecycle. Developers benefit from rapid feedback when new builds are automatically deployed into test environments, while operations benefits from running the same, test process, in production to avoid mistakes. With IBM UrbanCode Release, release planning is streamlined. Developers and testers can easily capture configuration and infrastructure tweaks made to labs that will need to be repeated in production. Meanwhile, release managers can easily see which projects are trending towards completion and which might miss the release train.

Scenario 2: Coordinating Change

Making sure what was tested together is released together

Applications are increasingly assembled out of interdependent services and components. Keeping track of what has been tested together, and what should be released together is increasingly a challenge. IBM UrbanCode Deploy models applications as a collection of component parts. When tests pass, it can create a “Snapshot.” IBM UrbanCode Release is built to track operational releases containing many related application and infrastructure changes. It generates a manifest of all changing applications known as a “Release Version” to create a unit of promotion that spans applications. With impact analysis, and deployment day orchestration, UrbanCode Release helps delivery teams stay in control.