Enterprise DevOps
Enterprise DevOps
$12.00
Minimum
$14.00
Suggested
Enterprise DevOps

This book is 50% complete

Last updated on 2016-10-30

About the Book

  • Important: This book is still in beta and is only partially finished. You can purchase it now for a lower price and you'll automatically get the full book when it's done as well as notifications when it continuously updates.
  • You can also find a whole bunch of videos explaining concepts from this book at http://enterprisedevops.org

Enterprise DevOps is the application of DevOps values in an environment that contains any of the following:

  • Many inter-dependent and related systems and sub systems, software and teams that rely on each other
  • Monolithic systems and/or static software/hardware environments
  • Lengthy Approval Gates or change control processes
  • Security, financial, medical or other compliance requirements
  • Lengthy waterfall based processes among multiple teams and stake holders
  • Workflows that are mostly manual and error prone across multiple teams or stakeholders

In order to create an organization that operates through automated pipelines of continuous delivery.

Table of Contents

  •  
    •  
      • About the Author
  • I Introduction
    • 1. What is Enterprise DevOps?
      •  
        • What is DevOps? (Version 0.1)
      • 1.1 What is Enterprise DevOps?
      • 1.2 DevOps Metrics
        • Mean time to change (MTTC)
        • Mean time to recovery (MTTR)
        • Frequency of release
        • Amount of defects
    • What’s the point of Continuous Delivery?
    • Tests and Builds are Made to be Broken
      •  
        • The Blame Game:
        • Lost Productivity:
  • Separation of Concerns
    • Pattern: Build Script Injection
      •  
        • Other Names:
      • Problem:
      • Solution:
        • Source control side script
        • CI Side Scripts/Actions
      • Summary
    • Build Pattern: Fill In the Blanks
      • Other names:
      • Symptoms:
      • Problem:
      • Solution:
      • Possible Side Effects:
  • Productivity
    • Pattern: Shipping Skeleton
      •  
        • Other Names:
      • Problem:
      • Forces:
      • Solution:
        • Basic Shipping Skeleton Structure:
      • Summary
    • Pattern: Pipeline Disintegration
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
        • A more explicit example:
    • Accumulative Builds
      • Symptoms:
      • Problem:
      • Forces:
      • Solution
        • Example:
    • Build Decomposition: Incremental Feedback Loops
      • Other Names:
      • Symptoms
      • Problem
      • Forces
      • Solution
    • Pattern: Gated Commit
      • Other names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
      • Examples:
      • Side effects:
    • Avoid XML-As-UI
  • Maintainability
    • Fishbone Build Structure
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
      • Example
      • Summary
    • Build Pattern: Location Agnostic Script
      • Symptoms:
      • Problem:
      • Solution:
    • Extract Script
      • Symptoms:
      • Problem:
      • Solution
      • Example:
      • Possible Side Effects
    • Extract Build Configuration Template
      • Symptoms:
      • Problem:
      • Solution
        • Example:
        • Another common example:
        • Base_VersionedBuild
    • Base Parameter
      • Symptoms:
      • Problem:
      • Solution
      • Example:
  • Team Collaboration
    • Dependency Stash
      •  
        • Other Names:
      • Context
      • Symptom:
      • Problem:
        • The CI server
        • The Developer of the component
      • Forces:
        • In short:
      • Solution
        • Example
          • On the developer’s machine
    • Pattern: Version by Snapshots Dependencies
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
        • The Dilemma
        • Having it both ways
      • Summary
    • Pattern: Tipping Point
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
      • Summary
    • Pattern: Public API Hook
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
      • Summary
  • Stakeholder Patterns
    • Pattern: Deploy by Proxy
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
      • Example:
      • Summary
    • Pattern: Parallel Fire-hose
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
      • Example:
        • work flow 1: Fully automated Pipeline
        • work flow 2: Pull Based QA Pipeline
      • Summary
  • Branching Patterns
  • Scalability Patterns
    • Fan Out Agents
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Solution:
      • Example
    • Split To Parallel
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Solution:
      • Example
      • Step 1: Split the tests to runnable parts
      • Step 2: Create a parallel test run hierarchy in the CI server
  • Trustworthy Builds
    • Build Pattern: Binary Result
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Solution:
    • Irrelevant Build
      • Symptoms:
      • Problem:
      • Solution:
      • Example:
    • Big Ball of Mud Build
      •  
        • Other Names:
      • Symptoms:
      • Problem:
      • Forces:
      • Solution:
      • Summary

About the Author

Roy Osherove
Roy Osherove

Roy Osherove is the author of The Art Of Unit Testing, and has been in leadership roles for most of his professional life, acting as team lead, CTO and architect in many places. He's had many failures to learn from but also some great successes, that he likes to share by doing training courses and mentoring. You can read his blog at 5whys.com

About the Publisher

This book is published on Leanpub by Team Agile Publishing

Team Agile Publishing is Roy Osherove's publishing house.

The Leanpub 45-day 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

See full terms...

Write and Publish on Leanpub

Authors and publishers use Leanpub to publish amazing in-progress and completed ebooks, just like this one. You can use Leanpub to write, publish and sell your book as well! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub