The ABCs of Continuous Release and Deploy in a DevOps approach

Post on 11-May-2015

2.060 views 0 download

Tags:

description

The ABCs of Continuous Release and Deploy in a DevOps approach. Visit us on our page to learn more about UrbanCode, an IBM Company and our products - http://www.ibm.com/ibm/devops/us/en/deploy/release/

Transcript of The ABCs of Continuous Release and Deploy in a DevOps approach

The ABCs of ContinuousRelease and Deploy in a DevOps approach

This presentation is brought to you by:

Cleveland, OHIBM UrbanCode Products

UrbanCode Inc. Proprietary and Confidential ©2013

Your organization is struggling to keep up with business demand,

market trends, and customer

feedback.

UrbanCode Inc. Proprietary and Confidential ©2013

Your development teamhas transitioned to Agile, but are you really releasing your applications at the “speed of agile”?

Eric Naiburg
I don't think people would say they have "successfully transitioned..." I would write it more like "Your development teams have transitioned to Agile, but has it all been successful? With the Agile effort, applications..."

UrbanCode Inc. Proprietary and Confidential ©2013

There is a “wall” separating your customers from your business, development and operations

teams, keeping your organization from achieving the full benefits of Agile.

UrbanCode Inc. Proprietary and Confidential ©2013

So, how are you going to tear down that wall?

UrbanCode Inc. Proprietary and Confidential ©2013

DevOps

UrbanCode Inc. Proprietary and Confidential ©2013

The following slides focus on how to achieve Continuous Release

and Deploy as part of an overall DevOps approach

in 3 moves!

UrbanCode Inc. Proprietary and Confidential ©2013

Align teams

First Move

UrbanCode Inc. Proprietary and Confidential ©2013

With conflicting responsibilities, there is a natural tension between the Development and Operations teams.

Problem

UrbanCode Inc. Proprietary and Confidential ©2013

Solution

It’s important to coordinate and align teams with the same overall goals. To do so, teams must communicate early and often throughout the application delivery lifecycle.

UrbanCode Inc. Proprietary and Confidential ©2013

Build a

Second Move

consistent process

UrbanCode Inc. Proprietary and Confidential ©2013

Problem

Differing processes can result in failed deployments and production outages.

UrbanCode Inc. Proprietary and Confidential ©2013

Solution

Teams often share a single promotion process across the entire Software Delivery Lifecycle (SDLC).

UrbanCode Inc. Proprietary and Confidential ©2013

Create an

Third Move

automated culture

UrbanCode Inc. Proprietary and Confidential ©2013

Problem

Manual and “half-scripted” deployment steps can cause release failures and potential outages.

UrbanCode Inc. Proprietary and Confidential ©2013

Solution

Automate difficult steps to reduce the chances of manual or “half-scripted” steps leading to a break in production.

UrbanCode Inc. Proprietary and Confidential ©2013

The Continuous Release and Deploy practices with in DevOps approach will

result in accelerated time to market, stable and predictable releases

and fewer outages.

The Continuous Release and Deploy Practices as a part of a DevOps approach

will result in accelerated time-to-market, stable and predictable releases and fewer outages.

UrbanCode Inc. Proprietary and Confidential ©2013

Visit us on www.IBM.com

UrbanCode Inc. Proprietary and Confidential ©2013

Visit us on www.IBM.com