Untangling Continuous Delivery
24
description
The emerging software development methodology untangled.
Transcript of Untangling Continuous Delivery
• Fastest, most scalable, Version Management and Collaboration
• Commonly used for all types of content
– Code – Binaries – Movies – Chip Designs – Gaming – Images
Perforce OverviewGlobal Availability and Support
Versions Everything
Perforce Solves Critical Issues
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
& AnimaLon Cloud/SaaS Electronics Finance Enterprise
Analyst Perspective
Waterfall • Annual releases • Mostly manual
Agile • Release more than once a year
• Some automaLon
ConLnuous • Weekly/daily updates • Massive automaLon
“ The days when a successful organization could release software once every 12 to 18 months are over.
Forrester, “ConLnuous Delivery is reshaping the Future of ALM,”
Kurt BiWner, July 22, 2013
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 ExecuLves
How Familiar Are You with the Term “Con;nuous Delivery?”
According to a 2013 survey of US and UK so]ware professionals, conducted by Evans Data.
“What Does CD Mean to You?”“It’s a process to improve so]ware performance on a conLnual basis, with the use of automaLc triggers.” “It’s a process that
ensures conLnuous tweaks, addiLons and improvements to our so]ware systems.”
“The ability to conLnually adapt so]ware in line with user feedback and changes in business.”
“Releasing early and o]en so that the act of learning is accelerated, risk is idenLfied and you can react quicker.”
[ Automa;on ]
[ Time ]
[ Con;nuity ]
[ Process ]
65%
28%
User Data: Gaining Traction Fast
65% of so]ware developers, managers and execuLves report that their organizaLons have started down the path to Con;nuous Delivery
At Least Some Projects
All Projects
According to a 2013 survey of US and UK so]ware professionals, conducted by Evans Data.
It’s Not Just for SaaS Anymore
80% of SaaS companies are pracLcing ConLnuous Delivery
• 47% across ALL projects • 33% across some projects
All Projects At Least Some Projects
18% 51%
Non-‐SaaS Companies
According to a 2013 survey of US and UK so]ware professionals, conducted by Evans Data.
What’s Driving the Move?Faster Time to Market
BeWer Quality Product
CompeLLve Advantage
Customer SaLsfacLon
Lower Costs
According to a 2013 survey of US and UK so]ware professionals, conducted by Evans Data.
Keeping up with the Joneses
46% think their compeLtors have fully embraced ConLnuous Delivery
According to a 2013 survey of US and UK so]ware professionals, conducted by Evans Data.
Perforce CustomersSo]ware
Dev Code Review
ConLnuous IntegraLon Metrics QA Staging &
Release
HW Layout Chip Rev Firmware OS Apps
So]ware Dev
ConLnuous IntegraLon QA Analysis ConLnuous
Delivery Rollback
So]ware Dev
ConLnuous IntegraLon QA Staging Deployed
Binaries ConLnuous VerificaLon
Instant Rollback Capability
“THE” Cloud
BeaLng Apple
ObsoleLng DVDs
TWTR Picks NYSE
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
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!
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.)
Key RequirementsComplete Visibility Distributed Teams Flexible Workflow
Scalable & Performant Universal Security Unified Repository
P I P E L I N E Req’s Dev Test Integrate Deploy
HQ
Integrates With Your Pipeline
Developer CollaboraLon
Swarm
Design CollaboraLon
Commons
Development AnalyLcs
Insights
Perforce Version Management
100s of Terabytes Globally Distributed DVCS Any File Type
P4 Git
End-‐to-‐end CollaboraLon
Unified Asset Versioning
P I P E L I N E Req’s Dev Test Integrate Deploy
DEV
DEV
HQ
MFG
Rich Ecosystem of PartnersAgile ALM IDEs Code Review Build/CI Quality Deployment
In Summary: Untangling in 5 steps1. Think beyond the code – version
everything 2. Automate, automate, automate 3. Make everything fully visible 4. Track every change 5. Put it all in one place
hWp://www.meetup.com/UK-‐Perforce-‐Meetup-‐Group/
hWp://www.meetup.com/London-‐ConLnuous-‐Delivery/
