Boston 2015
The DevOps Tool Kit
Building the Software Supply Chain
Boston 2015
Boston 2015
March 18, 2015
Boston 2015
Why did 44,000 people
access this deck?
Boston 2015
The Software Supply Chain
Fewer
Suppliers
Better Parts
from those
Suppliers
Track and
Monitor
those Parts
Boston 2015
Why is this
important?
Boston 2015
Boston 2015
Boston 2015
Boston 2015
Boston 2015
A sample of the
architectures
Boston 2015
Geoffrey Waren
Boston 2015
Akshat Sharma
Boston 2015
Zhao Zhuo
Boston 2015
Alex Honor
Boston 2015
Hervé Leclerc
Boston 2015
Damon Edwards
Boston 2015
David Cramer
Boston 2015
Common Tools
in the DevOps Tool Kit
Boston 2015
Boston 2015
Continuous Everything
Fewer
Suppliers
Better Parts
from those
Suppliers
Track and
Monitor
those Parts
Boston 2015
Get the deck and
resources immediately…
Boston 2015
Community@Sonatype.com

The DevOps Tool Kit: Building the Software Supply Chain

Editor's Notes

  • #2 Splash screen: The DevOps Toolkit – Building the Software Supply Chain DevOpsDays Boston 2015 Lightning Talk
  • #3 About Me: Mark Miller Developer Evangelist and Senior Storyteller for TheNEXUS Community Project Executive Producer for the OWASP 24/7 Podcast Series
  • #4 On March 18, 2015, Derek Weeks published a slidedeck on Slideshare.net containing 31 reference architectures for DevOps and Continuous Delivery
  • #5 44,000 people accessed the deck. Why? They were looking for validation and ideas, comparing their reference architectures against the rest of the world.
  • #6 The Software Supply Chain is built upon three principles: Fewer Suppliers Better Parts from those Suppliers Track and Monitor those Parts
  • #7 Why is the concept of a software supply chain important?
  • #8 Interview with Debbie Edwards, Vice President, IBM Rational DevOps Capabilities Development  http://www.sonatype.org/nexus/2014/12/11/dibbe-edwards-devops-and-open-source-at-ibm/
  • #9 2015 State of the Software Supply Chain Report
  • #10 In the 8 years since 2007, download requests for components from the Central Repository have grown 30 fold. The only way to manage the use of that many components is through the use of automation… Continuous Integration, Continuous Delivery, Continuous Everything… as part of the software supply chain.
  • #12 44,000 people accessed the deck. Why? They were looking for validation and ideas, comparing their reference architectures against the rest of the world.
  • #20 What do we see in common with these architectures?
  • #21 When you look closely at the reference architectures, you’ll find a common set of tools recurring.
  • #23 What do we see in common with these architectures?
  • #24 Send an email to Community@Sonatype.com and receive an immediate response with links to resources from this deck.