Continuous Delivery: The New Normal. London Event

Welcome & Introductions

Mike Griffiths Perforce

[email protected] @p4mike

•  Fastest, most scalable, Version Management and Collaboration

•  Commonly used for all types of content

–  Code –  Binaries –  Movies –  Chip Designs –  Gaming –  Images

Perforce Overview Global Availability and Support

Perforce Solves Critical Issues

Versions Everything

Development

The image cann

Development

The

Manufacturing Headquarters

The image cannot

Massive Scalability From 10 to 10,000+ on a each trunk/mainline

Flexibility Distributed or centralized workflows

Collaboration Comprehensive review and pre-flight checks

Multi-site Teams Enables geographically distributed organizations

Big Stuff Efficiently handles large, often binary, data

Secure Unified policies, auditing and compliance

Industry Leaders Depend on Perforce

13,000 à 20,000 users

9,500 users 500+ terabytes

5,000+ users coders & designers

Complete delivery pipeline

7,000+ releases/year 11,000+ users

10+ sites

2,500 users 10,000,000

Perforce xact/day

Everything! 11,000+ users

Mobile ICs Games

& AnimaKon Cloud/SaaS Electronics Finance Enterprise

Agenda 14:00 Welcome & Introductions

14:15 Keynote: Continuous Delivery: The New Normal - Evans Data Research

15:00 Powering Continuous Delivery Pipelines by Next Generation Configuration Management Joris de Winne, XebiaLabs

15:45 Break

16:00 Customer Success with Continuous Delivery

16:30 Panel Discussion

17:00 Networking Drinks @ The Vintry

Continuous Delivery The New Normal

Mark Warren Perforce

[email protected] @mark_warren

Continuous Delivery Adoption •  Evans Data Corporation surveyed 600

software professionals •  300 in the U.S. & 300 in the U.K. •  1/3rd Developers, 1/3rd Managers and

1/3rd Executives •  Company size > 100 employees

Growing Awareness

Not at all

Somewhat familiar

Very familiar

I live and breath it

Developers Managers ExecuKves

How Familiar Are You with the Term “Con;nuous Delivery?”

According to a 2013 survey of US and UK soSware professionals, conducted by Evans Data.

“What Does CD Mean to You?” “It’s a process to improve soSware performance on a conKnual basis, with the use of automaKc triggers.” “It’s a process that

ensures conKnuous tweaks, addiKons and improvements to our soSware systems.”

“The ability to conKnually adapt soSware in line with user feedback and changes in business.”

“Releasing early and oSen so that the act of learning is accelerated, risk is idenKfied and you can react quicker.”

[ Automa;on ]

[ Time ]

[ Con;nuity ]

[ Process ]

65%

28%

User Data: Gaining Traction Fast

65% of soSware developers, managers and execuKves report that their organizaKons have started down the path to Con;nuous Delivery

At Least Some Projects

All Projects


It’s Not Just for SaaS Anymore

80% of SaaS companies are pracKcing ConKnuous Delivery

•  47% across ALL projects •  33% across some projects

All Projects At Least Some Projects

18% 51%

Non-‐SaaS Companies


What’s Driving the Move? Faster Time to Market

Befer Quality Product

CompeKKve Advantage

Customer SaKsfacKon

Lower Costs


Keeping up with the Joneses

46% think their compeKtors have fully embraced ConKnuous Delivery


Think There’s a Practical Path to Success

More than 5 years

3-‐5 years

1-‐2 years

6-‐12 months

< 6 months Developers Managers ExecuKves

How Long Does It Take to Migrate to Con;nuous Delivery?


Biggest Barriers

•  SaaS companies see lack of skilled people as the biggest barrier

•  Non-SaaS companies think the biggest barrier is getting technologies to work together

Gekng Technologies to Integrate

Lack of Skilled People

Lack of CollaboraKon

Lack of Visibility across Stages


Ready or Not? Staff

Technology

Process

Corporate Culture

Ready Somewhat ready Not ready at all


Collaboration is Critical

95% see their collaboraKon plamorm* as important to ConKnuous Delivery

* Version management, build automaKon, code review, etc.


Analyst Perspective

Waterfall •  Annual releases •  Mostly manual

Agile •  Release more than once a year

•  Some automaKon

ConKnuous •  Weekly/daily updates •  Massive automaKon

“ The days when a successful organization could release software once every 12 to 18 months are over.

Forrester, “ConKnuous Delivery is reshaping the Future of ALM,”

Kurt Bifner, July 22, 2013

P I P E L I N E

Continuous Delivery •  Deliver working product to users as quickly as possible •  Every change (check-in) leads to a potential release •  Give business the option to release – what, when, to whom •  A change in process, and culture

Con;nuous Delivery

Reqs Dev Test Integrate Deploy

Perforce Customers SoSware

Dev Code Review

ConKnuous IntegraKon Metrics QA Staging &

Release

HW Layout Chip Rev Firmware OS Apps

SoSware Dev

ConKnuous IntegraKon QA Analysis ConKnuous

Delivery Rollback

SoSware Dev

ConKnuous IntegraKon QA Staging Deployed

Binaries ConKnuous VerificaKon

Instant Rollback Capability

“THE” Cloud

BeaKng Apple

ObsoleKng DVDs

TWTR Picks NYSE

P I P E L I N E

Principles of Continuous Delivery

1 2 3 4 5 6

Automate almost everything

Keep everything in version control Doc Code Libraries Media Scripts Configs Binaries “Hardware”

(virtual)

If it hurts, do it more frequently

Build quality in

Done means released

Everybody is responsible

ConKnuous improvement

Repeatable process for release

Reqs Dev Test Integrate Deploy

Massive Impact on Development Con;nuous Delivery


Build quality in

Done means released



1 2 3 4 5 6



Keep everything in version control

Builds: Nightly à Hourly à Every Push Push: Weekly à Daily à Hourly à Each Change Releases: Yearly à Quarterly à Monthly à Daily Artifacts: Code à Content à Binaries Code: Home Grown à + 3rd Party à + Open Source

Teams: Small à Big à Distributed à Global

P I P E L I N E

Con;nuous Delivery


Build quality in

Done means released



1 2 3 4 5 6



Keep everything in version control

C O O R D I N A T E A S S E T S (code, scripts, artwork, binaries, etc.)

C O O R D I N A T E T E A M S (design, dev, release, devops, etc.)

Managing Continuous Delivery

C O O R D I N A T E A S S E T S (code, scripts, artwork, binaries, etc.)

C O O R D I N A T E T E A M S (design, dev, release, devops, etc.)

P I P E L I N E

Key Requirements Complete Visibility Distributed Teams Flexible Workflow

Scalable & Performant Universal Security Unified Repository

End-‐to-‐end CollaboraKon

Unified Asset Versioning

Perforce Versioning & Collaboration

P I P E L I N E

Developer CollaboraKon

Swarm

Design CollaboraKon

Commons

Development AnalyKcs

Insights

Perforce Version Management

100s of Terabytes Globally Distributed DVCS Any File Type

P4 Git DEV

DEV

HQ

MFG

Integrates With Your Pipeline

Developer CollaboraKon

Swarm

Design CollaboraKon

Commons

Development AnalyKcs

Insights

Perforce Version Management

100s of Terabytes Globally Distributed DVCS Any File Type

P4 Git DEV

DEV

HQ

MFG

End-‐to-‐end CollaboraKon

Unified Asset Versioning

P I P E L I N E Req’s Dev Test Integrate Deploy

Rich Ecosystem of Partners Agile ALM IDEs Code Review Build/CI Quality Deployment

Quantifying the Power of Perforce Forrester Total Economic Impact Study Conducted analysis of 4 Perforce customers across industries/geographies

•  A Fortune 500 computer storage and appliance

•  A multinational computer software company

•  An Asia-Pacific semiconductor manufacturer

•  A US-based commercial bank

•  Developed a risk-adjusted financial model representing the characteristics & results of the interviewed companies

•  Created an adaptive estimator that can be applied to any organization for a customized ROI assessment

Quantifying the Power of Perforce Forrester’s 2014 Total Economic Impact Study shows… •  10% - 15% increase in developer productivity

•  Saving on hardware, admin, support & maintenance

•  Less custom integration

•  25% faster time to market

•  Payback in < 4 months

•  ROI of 582%

.

In Summary: 5 Habits for Success 1.  Think beyond the code 2.  Automate, automate, automate 3.  Make everything fully visible 4.  Track every change 5.  Put it all in one place

Customer Success with Continuous Delivery

Mike Griffiths Perforce

Habits of Highly Successful Continuous Delivery Practitioners

Expert Panel: Continuous Delivery Best Practices Revealed

About Intuit •  Passion for inventing solutions to solve important

problems •  Engineering staff of 4000+ across 6+ sites

worldwide

•  Must be very nimble to meet ever-changing tax, personal-income and business-regulatory laws

Adoption at Intuit •  TurboTax

–  Automatic build and delivery work flow

–  Secure and elastic private cloud environment

•  QuickBooks –  Reduce build time from several hours to less than a hour

–  Optimized build scripts and centralizing build farm.

•  Intuit Live Community –  builds, tests, and deploys itself, continuously, in a public cloud infrastructure.

About edmunds.com •  edmunds.com helps you find the Exact Car you want - from Research to

Purchase.

•  Monthly 18M+ unique visitors, 200M+ page views.

•  Presence on Wired, Mobile, Externally exposed APIs

•  Progression from Waterfall to Agile to Iterative Scrum and now to Continuous Delivery

•  Activities 24x7

Adoption at edmunds.com •  End-to-end continuous delivery

•  Fully automated builds, testing and promotion to production environments

•  Helped foster Innovation & Rapid Experimentation

•  Code Stability {infrastructure, product, configuration, tests}

•  Faster resolutions to issues

About Tableau Software •  We help people see and understand their data.

Adoption and Practices •  Distributed, highly parallel development

–  Waterfall → Agilefall → Agile –  Release train (sustaining → new development)

•  Quality first (QSF) –  Implicit core value → explicit priority

•  Infrastructure as code –  Agile development (product functionality → all engineering) –  Configuration management principles (product → all)

Common Themes •  Architectural design is key

–  “Move from spaghetti to a layered cake” •  Build in adoption and confidence •  Quality as standard •  Infrastructure as Product

–  Submit configurations to Version Management –  Treat systems as products –  Testing as products

•  Mainline / trunk

Version at Scale •  First code check in: 1998

•  7800 users (88% of employees)

•  80,000,000 transactions/day

•  198 instances

(55 RW, 14 RO, 4 Brokers and 125 scratch)

•  556 Million files comprising 1.3 Billion

revisions

•  327 TB of data

Versioning enables massive growth

“ If it’s not in Perforce it doesn’t exist

Version Everything •  Version “absolutely everything”

•  Branching – “where it makes sense”

•  “Nobody is born a versioning hero”

Versioning is the nerve centre of the organiza;on

“ Versioning everything takes an investment, it’s worth it.

Halldor Fannar, CTO

Mainline Model •  150 teams, 5,000 testing VMs, 500,000 files.

•  Up to 10 million Perforce transactions per

day, heading towards 15 – 20 million

•  Mainline code model

•  Fast feedback is key

•  Security, audit, compliance. Easy audit

process

Mainline is cri;cal to collabora;on

“ Doubling the transactions, no increase in admins

Mainline Branching Strategy

Release 1.1.x

Release 1.0.x R R R

R R merge bugfix

merge bugfix

•  Visibility •  Always deployable •  ConKnuous IntegraKon, only

create branches for releases

Mainline

•  Manage what gets into mainline •  ConKnuous IntegraKon •  Code Review

System of Record •  14,000 servers, 6,600 production

releases per year, 198+ active projects

•  Build artifacts stored in Perforce

•  Version management enforces security

•  Deploy “bridge” into production &

rollback

Single Source of Truth

“ Perforce is boring!

Versioning Samsung… •  World’s most successful

Android company

•  13,000 users that version

hardware, firmware, software –  mobile, television,

semiconductor

•  Worldwide development

in 12+ countries

All Android Development Done in Perforce

320 Git repositories Perforce Samsung