learning from the early adopters of devops: a guidebook to success featuring forrester research

© Perforce Software Inc. All Rights Reserved.

Learning from the Early Adopters of DevOpsA Guidebook to Success from Forrester Research

2© Perforce Software Inc. All Rights Reserved.

Amy DeMartine Sr. Analyst Serving Infrastructure &

Operations Professionals

Forrester Research

John WillistonProduct Marketing Manager &

Developer Evangelist

Perforce Software

Learning From The Early Adopters Of DevOpsAmy DeMartine, Principal Analyst

© 2015 Forrester Research, Inc. Reproduction Prohibited 5

Source: “Boost Application Delivery Speed And Quality With Agile DevOps Practices”, Forrester report

Application Release Cycles Are Long…


Source: “Six Trends That Will Shape DevOps Adoption In 2016 And Beyond”, Forrester report

And The Business Isn’t Happy


DevOps provides a set of practices and cultural changes — supported by complementary tools — that automates the software delivery pipeline, enabling organizations to win, serve, and retain consumers better and faster than ever before.

Source: “Brief: The State Of DevOps Industry Adoption For 2016 — Where's The Heat?” Forrester report.


Source: “DevOps Makes Modern Service Delivery Modern”, Forrester report

Goal is continuous delivery…



Typical Application Release Bottlenecks



Key Delivery Practices And The Release Cycles They Enable (Part 1)


51% of respondents claimed partial version control but only 37% claim full version control of all artifacts in the continuous delivery pipeline.

Source:. Q1 2016 Global Modern Service Delivery Benchmark Online Survey, Base 142 I&O professionals., Forrester report


Source:. “The Quest For Speed-Plus-Quality Drives Agile And DevOps Tool Selection” Forrester report

Tools Help Glue The Continuous Delivery Pipeline Together


Key Takeaways›To transform customer experience and accelerate the digital business we need to release quicker.

›Releasing quicker relies heavily on automation but also strong processes and cultural shifts.

All This Has Happened Before…


A Trip Down Memory Lane


Developers• Little system access• Code in the closet• Every run unique• Versioning only by

duplicate decks, disks, tapes, etc.

In the Beginning

Operators• Unlimited access• Storage was precious• Every run a chore• System software

versioned by different tapes/disks


• Complexity forces unity, Dev + Ops• Tighter iteration -> better products• Automating the grunt work• Significant competitive advantages

Today’s DevOps Movement

DevOps Is Not One Size Fits All


• DevOps grew from the web• Comparatively small projects• Minimal legacy burdens• Largely simple deployment

The Ideal Case


• Legacy apps -> more work• Divide and conquer• CI first, then CT and CD• Evolutionary process

Legacy Applications


• Bringing contributors together• Driving down build cycles• Automating testing and validation• Automating staging and deployment• Managing / automating infrastructure• Securing and maintaining history

immutably in perpetuity

Common Goals

Enter Perforce Helix


• Old world: craftsmen and guilds• The industrial revolution:

• Sequenced units of work• Staged them all in a pipeline• Integrated those units of work• Tested and shipped the final

products/services• Doesn’t that sound familiar?

The Manufacturing Parallel


• The new world has dev, ops, and more

• In the DevOps movement:• Work delivered as units• Staged in a pipeline• Units integrated automatically• Testing, packaging, and

deployment are automated• All of this has happened

before…

The Modern Equivalent


• Plethora of clients, plugins, and tools• Proven federated server architecture• Branches, streams, advanced DVCS• Code review and collaboration• Broad integrations and APIs• The one system you’ll never outgrow

Helix is the Digital Assembly Line


DevOps Pipeline Overview

Helix Versioning Engine

Infrastructure Management (i.e. Chef, Puppet)

Integration (CI) Test (CT) Delivery (CD)Contributors Customers


• Tearing down silos• Component based

development• Minimize cycle times• Performance and scalability• Artifact management

Continuous Integration


IM Tool (i.e. Chef, Puppet)Manage Artifacts

Build Tool Check in/Check out

RC


• Test document storage• Scripting automation• Environment storage• Automated provisioning• Acceptance testing• Validation and

verification

Continuous Testing


IM Tool (i.e. Chef, Puppet)

Test (CT)

Release

Test Scripts


• Final signing / stamping• Retain installers / packages• Infrastructure as code• Automated provisioning• Staging <-> production swap• Compliance reporting

Continuous Delivery


IM Tool (i.e. Chef, Puppet)

Delivery (CD)Release

Log Data MD5 Signatures, etc.


• Infrastructure as code• Bare metal to node(s)• Node config / manage• Full orchestration• Store light containers• Store full VMs

Infrastructure Management


• Scania uses Perforce Helix• DevOps improved everything:

• Tore down the silos• United all contributors• Accelerated the build process• Took testing to a new level

• And that’s just the beginning

It’s Not Just Us

Amy DeMartine

@AmyDeMartine

Forrester Research

John Williston

@p4jbw

Perforce Software

Questions?

Thank you for attending!