© 2013 IBM Corporation

Mark Roberts

IBM Cloud IT Specialist

UrbanCode Deploy and Jenkins

DevOps approach Apply Lean principles accelerate feedback and improve time to value

Line-of-

business

Customer

Non-Value-added waste Value-added production work

Lean

Transformation

Where to start - DevOps Adoption Address bottlenecks in the Delivery Pipeline

Develop

/ Test Deploy Steer Operate

Collaborative Development

Continuous Release and Deployment

Continuous Testing

Business

Owner

Service

Developer/Tester

Service

Operations

Target

Customer

Idea Market

DevOps

Continuous

Business Planning

Continuous Monitoring

Lean and Agile principles

Continuous feedback and Optimization

Implementing a Delivery Pipeline

Smooth transition of value from left to right

Easy traceability and audit record looking right to left

Automation

– Speed

– Reliability

– Efficiency

– predictability

Challenge:

– Developers were creating daily builds

– QA team had a 3 – 5 day cycle time

Bottlenecks Identified:

1. Lack of Deployment Automation

2. Ticket based manual environment provisioning

3. Manual handover from build to deployment

Delivery Pipeline Optimization

Deploying Middleware and Infrastructure The biggest bottlenecks for the Delivery Pipeline

The adoption of DevOps

– Increased velocity of application delivery

Middleware changes can :

– Be complex

– Be slow

– Require co-ordination across teams

Pressure on the infrastructure

– Need to respond more quickly to change

– Support ‘what if’ scenarios

– Experimentation with runtime configurations

Software defined environments and configurations

– Capture infrastructure as a software artifact

– Portable deployable content

Application

Changes

Infrastructure

Changes

Pipeline

Middleware

configuration

UrbanCode Deploy

7