Keys to Continuous Delivery Success - Mark Warren, Product Director, Perforce Software
Download as PPTX, PDF3 likes1,364 views
The document outlines the importance of continuous delivery in software development, emphasizing the transition from traditional release methods to highly automated, rapid delivery cycles. It highlights that 65% of software professionals have begun adopting continuous delivery practices, indicating a significant shift in the industry. Key practices for success include automating processes, ensuring visibility, and maintaining comprehensive version control across all types of content.
![What Does Continuous Delivery
Mean to You?
6
“It’s a process to improve
software performance on a
continual basis, with the use
of automatic triggers.” “It’s a process that
ensures continuous
tweaks, additions and
improvements to our
software systems.”
“The ability to continually
adapt software in line with
user feedback and
changes in business.”
“Releasing early and often
so that the act of learning
is accelerated, risk is
identified and you can
react quicker.”
[ Automation ]
[ Time ]
[ Continuity ]
[ Process ]
Source: Evans Data research 2013](https://image.slidesharecdn.com/qconuk2014-perforcecontinuousdeliverypv1-140311082115-phpapp02/85/Keys-to-Continuous-Delivery-Success-Mark-Warren-Product-Director-Perforce-Software-6-320.jpg)
Keys to Continuous Delivery Success - Mark Warren, Product Director, Perforce Software
- 1. Keys to Continuous Delivery Success Mark Warren Product Director Perforce Software
- 2. • Enterprise Version Management • 10,500+ customers • Trusted with storing and versioning the most valuable IP for the world's most innovative companies – From start-ups to Fortune 100 – The leading cloud companies • All types of content Perforce Software – Chip Designs – Gaming – Images – Code – Binaries – Movies
- 3. Industry Perspective 3 Waterfall • Annual releases • Mostly manual Agile • Release more than once a year • Some automation Continuous • Weekly/daily updates • Massive automation “The days when a successful organization could release software once every 12 to 18 months are over. “Continuous Delivery is Reshaping the Future of ALM,” Kurt Bittner, Forrester, July 2013
- 4. Accelerated Delivery Means … 4 Nightly Hourly Every Check-in Yearly Quarterly Monthly Daily Code Content Binaries Home Grown 3rd Party +Open Source Small Big Distributed Global B U I L D S R E L E A S E S A R T I F A C T S C O D E T E A M S
- 5. Growing Awareness According to a 2013 survey of US and UK software professionals, conducted by Evans Data. Not at all Somewhat familiar Very familiar I live and breath it Developers Managers Executives How Familiar Are You with the Term “Continuous Delivery?”
- 6. What Does Continuous Delivery Mean to You? 6 “It’s a process to improve software performance on a continual basis, with the use of automatic triggers.” “It’s a process that ensures continuous tweaks, additions and improvements to our software systems.” “The ability to continually adapt software in line with user feedback and changes in business.” “Releasing early and often so that the act of learning is accelerated, risk is identified and you can react quicker.” [ Automation ] [ Time ] [ Continuity ] [ Process ] Source: Evans Data research 2013
- 7. Continuous Delivery – The New Normal 7 All Projects At Least Some Projects 28% 65%65%of software developers, managers and executives report that their Organizations have started down the path to Continuous Delivery Source: Evans Data research 2013
- 8. It’s Not Just for SaaS Anymore 80% of SaaS companies are practicing Continuous Delivery • 47% across ALL projects • 33% across some projects All Projects At Least Some Projects 18% 51% Non-SaaS Companies Source: Evans Data research 2013
- 9. Keeping up with the Joneses DEV BUILD DEV CUSTOMER QA V.P. RELEASE CompetitorsCompetitors 46% think their competitors have fully embraced Continuous Delivery Source: Evans Data research 2013
- 10. Product Delivery Pipeline 10 Requirements Develop Build Test Integrate Deploy
- 11. Product Delivery Pipeline 11 BuildRequirements Develop IntegrateTest Deploy Rqmts Doc Licenses/ IP History Social Coding Build Farms QA Results Scripts “Hardware” (Virtual) Code Open Source Binaries Release Binaries Code Open Source Binaries Release Binaries
- 12. Product Delivery Pipeline 12 BuildRequirements Develop IntegrateTest Deploy Rqmts Doc Licenses/ IP History Social Coding Build Farms QA Results Scripts “Hardware” (Virtual) Code Open Source Binaries Release Binaries Team Collaboration (design, dev, release, devops…) Accelerate the Pipeline (code, artwork, scripts, binaries, etc.)
- 13. Version Everything – CCP Games • Version absolutely *everything* – Instant workstation configuration • Branching – “where it makes sense” • “Nobody is born a versioning hero” • “Versioning everything requires an investment. It’s worth it.” Versioning is the nerve center of the organization{ }
- 14. 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 14
- 15. Mainline Release Branching Strategy Release 1.1.x Release 1.0.xRR R R R merge bugfix merge bugfix • Visibility • Always deployable • Continuous Integration, only create branches for releases • Manage what gets into mainline • Continuous Integration • Code Review Mainline
- 16. Mainline – Salesforce.com • 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 • “Perforce is boring” – For ops team, that’s a very good thing! Mainline is critical to collaboration{ }
- 17. Source Code Source Code Source Code Source Code Source Code Source Code Source Code Source Code Source Code Source Code Source Code Source Code Production serverProduction serverProduction serverProduction server Production serverProduction serverProduction serverProduction server Where is this code deployed? What changes have been made? What code has been reviewed? What has been tested? Did it pass? What work needs to be done? What’s running on each of these servers? Can I back changes out? What was running last night/week/month/ye ar? What needs to be deployed next? How many places are needed to answer the questions? How traceable? Single Source of Truth Chain of Custody System of Record
- 18. Single Source of Truth • How many processes to learn? • How many tool integrations to manage? • How many admins? • How to ensure availability? 18 SCM SCM SCMSCM
- 19. New challenges • Are both needed? • How to ensure traceability? • How to provide audit trails? • How to manage access controls? • How many admins, processes, tools, …? 19 SCM - Source Code - Build Scripts - Test scripts - … Artifact Repository - Built executables - Databases - …
- 20. System of Record – NYSE • 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”{ }
- 21. Perforce Overview 21 • Fastest, most scalable, Version management platform • Commonly used for all types of content – Code – Binaries – Movies – Chip Designs – Gaming – Images
- 22. Perforce Software 22 13,000 20,000 users 9,500 users 500+ terabytes Complete Delivery Pipeline 7,000+ releases/year SaaS Mobile IC’s Enterprise Cloud Finance Electronics Animation Gaming 11,000+ users 10+ sites 5,000+ users Coders & Designers Everything 2,500 users 10,000,000 Perforce xact/day 11,000+ users
- 23. Proven Platform for Continuous Delivery 23 Integrations
- 24. Best Habits for Success 1. 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
- 25. Prizes !!! • Perforce Stand – Floor 3 • Win a GoPro Camera 25
- 26. For more information For more use cases and information on the role of version management… perforce.com
- 27. 27