https://DevOpsCloud.io -- Cloud Monk Losang Jinpa, Ph.D., MCSE/MCT, GitOps DevOps Engineer

Return to Continuous Delivery by Jez Humble and David Farley, CI/CD, CI/CD Bibliography - CI/CD People, CI/CD, CI/CD and DevOps - CI/CD and SRE - Cloud Native and CI/CD - CI/CD and Microservices - Serverless CI/CD, CI/CD Security - CI/CD and DevSecOps, Functional Programming and CI/CD, CI/CD Concurrency, CI/CD and Data Science - CI/CD and Databases, CI/CD and Machine Learning, CI/CD Courses, CI/CD Glossary, Awesome CI/CD, CI/CD GitHub, CI/CD Topics

Fair Use Source: B003YMNVC0 (CDHumbFarl 2010)

“ (CDHumbFarl 2010)

Contents

Foreword

Preface

Acknowledgments

About the Authors

Part I: Foundations

Problem of Delivering Software

Chapter 1: The Problem of Delivering]] Software

• Introduction
• Some Common Release Antipatterns
• Antipattern: Deploying Software Manually
• Antipattern: Deploying to a Production]]-like Environment Only after Development Is Complete
• Antipattern: Manual Configuration Management of Production]] Environment]]s
• Can We Do Better?
• How Do We Achieve Our Goal?
• Every Change Should Trigger the Feedback Process
• The Feedback Must Be Received as Soon as Possible
• The Delivery Team Must Receive Feedback and Then Act on It
• Does This Process Scale?
• What Are the Benefits?
• Empowering Teams
• Reducing Errors
• Lowering Stress
• Deployment Flexibility
• Practice Makes Perfect
• The Release Candidate
• Every Check-in Leads to a Potential Release
• Principles of Software Delivery
• Create a Repeatable]] , Reliable Process for Releasing Software
• Automate Almost Everything
• Keep Everything in Version Control
• “If It Hurts, Do It More Frequently”, and Bring the Pain Forward
• Build Quality In
• Done Means Released]]
• Everybody Is Responsible for the Delivery Process
• Continuous Improvement
• Summary

Configuration Management

Chapter 2: Configuration Management

• Introduction
• Using Version Control
• Keep Absolutely Everything in Version Control
• Check In Regularly to Trunk
• Use Meaningful Commit Messages
• Managing Dependencies
• Managing External Libraries
• Managing Components
• Managing Software Configuration]]
• Configuration and Flexibility
• Types of Configuration
• Managing Application Configuration
• Managing]] Configuration across Applications
• Principle]]s of Managing Application Configuration
• Managing Your Environments
• Tool]]s to Manage Environments
• Managing]] the Change Process
• Summary

Continuous Integration

Chapter 3: Continuous Integration]]

• Introduction
• Implementing Continuous Integration]]
• What You Need Before You Start
• A Basic Continuous Integration]] System
• Prerequi[[sites for Continuous Integration]]
• Check In Regularly
• Create a Comprehensive Automated Test Suite
• Keep the Build and Test Process Short
• Managing Your Development Workspace
• Using Continuous Integration]] Software
• Basic Operation
• Bells and Whistles
• Essential Practices
• Don't Check In on a Broken Build
• Always Run All Commit Tests Locally before Committing, or Get Your CI Server to Do It for You
• Wait for Commit Tests to Pass before Moving On
• Never Go Home on a Broken Build
• Always Be Prepared to Revert to the Previous Revision
• Time-Box Fixing before Reverting
• Don't Comment Out Failing Tests
• Take Responsibility for All Breakages That Result from Your Changes
• Test-[[Driven Development]]
• Suggested Practices
• Extreme Programming (XP) Development Practices
• Failing a Build for Architectural Breaches
• Failing the Build for Slow Tests
• Failing the Build for Warnings and Code [[Style Breaches
• Distributed Teams
• The Impact on Process
• Centralized Continuous Integration]]
• Technical Issues
• Alternative]] Approaches
• Distributed Version Control Systems
• Summary

Implementing a Testing Strategy

Chapter 4: Implementing a Testing Strategy

• Introduction
• Types of Tests
• Business-Facing Tests That Support the Development Process
• Technology-Facing Tests That Support the Development Process
• Business-Facing Tests That Critique the Project
• Technology-Facing Tests That Critique the Project
• Test Doubles
• Real-Life Situations and Strategies
• New Projects
• Midproject
• Legacy System]]s
• Integration Testing
• Process
• Managing Defect Backlogs
• Summary

Part II: The Deployment Pipeline

Anatomy of the Deployment Pipeline

Chapter 5: Anatomy of the Deployment Pipeline

• Introduction
• What Is a Deployment Pipeline?
• A Basic Deployment Pipeline
• Deployment Pipeline Practices
• Only Build Your Binaries Once
• Deploy the Same Way to Every Environment
• Smoke-Test Your Deployments
• Deploy into a Copy of Production]]
• Each Change Should Propa[[gate through the Pipeline Instantly
• If Any Part of the Pipeline Fails, Stop the Line
• The Commit Stage
• Commit Stage Best Practices
• The Automated Acceptance]] Test Gate
• Automated Acceptance]] Test Best Practices
• Sub]]sequent Test Stages
• Manual Testing
• Nonfunctional]] Testing
• Preparing]] to Release
• Automating]] Deployment and Release
• Backing]] Out Changes
• Building on Success
• Implementing a Deployment Pipeline
• Modeling]] Your Value Stream and Creating a Walking Skeleton
• Automating the Build and Deployment Process
• Automating the Unit Test]]s and Code [[Analysis
• Automating]] Acceptance]] Tests
• Evolving]] Your Pipeline
• Metric]]s
• Summary

Build and Deployment Scripting

Build and Scripting

Chapter 6: Build and Deployment Scripting

Introduction

An Overview of Build Tools

Make

Ant

NAnt and MSBuild

Maven

Rake

Buildr

Psake

Principles and Practices of Build and Deployment Scripting

Create a Script for Each Stage in Your Deployment Pipeline

Use an Appropriate Technology to Deploy Your Application

Use the Same Scripts to Deploy to Every Environment

Use Your Operating System’s Packaging Tools

Ensure the Deployment Process Is Idem[[potent

Evolve Your Deployment System Incrementally

Project Structure for Applications That Target the JVM

Project Layout

Deployment Scripting

Deploying and Testing Layers

Testing Your Environment’s Configuration

Tips and Tricks

Always Use Relative Paths

Eliminate Manual Steps

Build In Traceability from Binaries to Version Control

Don't Check Binaries into Version Control as Part of Your Build

Test Targets Should Not Fail the Build

Constrain Your Application with Integrated Smoke Tests

.NET Tips and Tricks

Summary

Chapter 7: The Commit Stage

Introduction

Commit Stage Principles and Practices

Provide Fast, Useful Feedback

What Should Break the Commit Stage?

Tend the Commit Stage Carefully

Give Developers Ownership]]

Use a Build Master for Very Large Teams

The Results of the Commit Stage

The Artifact Repository

Commit Test Suite Principles and Practices

Avoid the User Interface

Use Dependency Injection

Avoid the Database

Avoid Asynchrony in Unit Test]]s

Using Test Doubles

Minimizing State in Tests

Faking Time

Brute Force

Summary

Chapter 8: Automated Acceptance]] Testing

Introduction

Why Is Automated Acceptance]] Testing Essential?

How to Create Maintainable Acceptance]] Test Suites

Testing against the GUI

Creating Acceptance]] Tests

The Role of Analysts and Testers

Analysis on Iterative Projects

Acceptance]] Criteria as Executable Specifications

The Application [[Driver Layer

How to Express Your Acceptance]] Criteria

The Window Driver Pattern: De[[coupling the Tests from the GUI

Implementing Acceptance]] Tests

State in Acceptance]] Tests

Process Boundaries]], Encapsulation, and Testing

Managing Asynchrony and Timeouts

Using Test Doubles

The Acceptance]] Test Stage

Keeping Acceptance]] Tests Green

Deployment Tests

Acceptance]] Test Performance

Refactor Common Tasks

Share Expensive Resources

Parallel Testing

Using Compute Grids

Summary

Chapter 9: Testing Nonfunctional Requirements

Introduction

Managing Nonfunctional Requirements

Analyzing Nonfunctional Requirements

Programming for Capacity

Measuring Capacity

How Should Success and Failure Be Defined for Capacity Tests?

The Capacity-Testing Environment

Automating Capacity Testing

Capacity Testing via the User Interface

Recording Interactions against a Service or Public API

Using Recorded Interaction Templates

Using Capacity Test Stubs to Develop Tests

Adding Capacity Tests to the Deployment Pipeline

Additional Benefits of a Capacity Test System

Summary

Chapter 10: Deploying and Releasing Applications

Introduction

Creating a Release Strategy

The Release Plan

Releasing Products

Deploying and Promoting Your Application

The First Deployment

Modeling Your Release Process and Promoting Builds

Promoting Configuration

Orchestration

Deployments to Staging Environments

Rolling Back]] Deployments and Zero-Downtime Releases

Rolling Back]] by Redeploying the Previous Good Version

Zero-Downtime Releases

Blue-Green Deployments

Canary Releasing

Emergency Fixes

Continuous Deployment

Continuously]] Releasing User-Installed Software

Tips and Tricks

The People Who Do the Deployment Should Be Involved in Creating the Deployment Process

Log Deployment Activities

Don't Delete the Old Files, Move Them

Deployment Is the Whole Team’s Responsibility

Server Applications Should Not Have GUIs

Have a Warm-Up Period for a New Deployment

Fail Fast

Don't Make Changes Directly on the Production]] Environment]]

Summary

Part III: The Delivery Ecosystem

Chapter 11: Managing Infrastructure]] and Environments

Introduction

Understanding the Needs of the Operations Team

Documentation and Auditing

Alerts for Ab[[normal Events

IT Service Continuity Planning

Use the Technology the Operations Team Is Familiar With

Modeling and Managing Infrastructure]]

Controlling Access to Your Infrastructure]]

Making Changes to Infrastructure]]

Managing Server Pro[[visioning]] and Configuration

Pro[[visioning]] Servers

Ongoing Management of Servers

Managing the Configuration of Middleware

Managing Configuration

Research the Product

Examine How Your Middleware Handles State

Look for a Configuration API

Use a Better Technology

Managing Infrastructure]] Services

Multihomed Systems

Virtualization

Managing Virtual Environment]]s

Virtual Environment]]s and the Deployment Pipeline

Highly Parallel Testing with Virtual Environment]]s

Cloud Computing

Infrastructure]] in the Cloud

Platforms in the Cloud

One Size Doesn’t Have to Fit All

Criticisms of Cloud Computing

Monitoring]] Infrastructure]] and Applications

Collecting Data

Logging

Creating Dash[[boards

Behavior-Driven Monitoring]]

Summary

Chapter 12: Managing Data

Introduction

Database Scripting

Initializing Databases

Incremental Change

Versioning Your Database

Managing Orchestrated Changes

Rolling Back]] Databases and Zero-Downtime Releases

Rolling Back]] without Losing Data

De[[coupling Application [[Deployment from Database [[Migration

Managing Test Data

Faking the Database for Unit Test]]s

Managing the Coupling between Tests and Data

Test Isolation

Setup and Tear Down

Coherent Test Scenarios

Data Management and the Deployment Pipeline

Data in Commit Stage Tests

Data in Acceptance]] Tests

Data in Capacity Tests

Data in Other Test Stages

Summary

Chapter 13: Managing Components and Dependencies

Introduction

Keeping Your Application Releasable

Hide New Functionality Until It Is Finished

Make All Changes Incrementally

Branch by Abstraction

Dependencies

Dependency Hell

Managing Libraries

Components

How to Divide a Codebase into Components

Pipelining Components

The Integration Pipeline

Managing Dependency Graphs

Building Dependency Graphs

Pipelining Dependency Graphs

When Should We Trigger Builds?

Cautious Optimism

Circular Dependencies

Managing Binaries

How an Artifact Repository Should Work

How Your Deployment Pipeline Should Interact with the Artifact Repository

Managing Dependencies with Maven

Maven Dependency Refactoring]]s

Summary

Chapter 14: Advanced Version Control

Introduction

A Brief History of Revision Control

CVS

Subversion

Commercial Version Control Systems

Switch Off Pessimistic Locking

Branching]] and Merging

Merging

Branches, Streams, and Continuous Integration]]

Distributed Version Control Systems

What Is a Distributed Version Control System?

A Brief History of Distributed Version Control Systems

Distributed Version Control Systems in Corporate Environments

Using Distributed Version Control Systems

Stream-Based Version Control Systems

What Is a Stream-Based Version Control System?

Development Models with Streams

Static and Dynamic View]]s

Continuous Integration]] with Stream-Based Version Control Systems

Develop on Mainline

Making Complex Changes without Branching]]

Branch for Release

Branch by Feature

Branch by Team

Summary

Chapter 15: Managing Continuous Delivery

Introduction

A Maturity Model for Configuration and Release Management

How to Use the Maturity Model

Project Lifecycle

Identification

Inception

Initiation

Develop and Release

Operation

A Risk Management Process

Risk Management 101

Risk Management Timeline

How to Do a Risk-Management Exercise

Common Delivery Problems — Their Symptoms and Causes

In[[frequent or Buggy Deployments

Poor Application Quality

Poorly Managed Continuous Integration]] Process

Poor Configuration Management

Compliance and Auditing

Automation over Documentation

Enforcing Traceability

Working in Silos

Change Management

Summary

Bibliography

Index

Fair Use Sources:

• Continuous Delivery by Jez Humble and David Farley on DuckDuckGo
• B003YMNVC0 (CDHumbFarl 2010)