book

Grokking Continuous Delivery

Name: Grokking Continuous Delivery
Author: Christie Wilson
ISBN: 9781617298257

by Christie Wilson

October 2022

Intermediate to advanced

424 pages

10h 34m

English

Manning Publications

Audiobook available

Read now

Unlock full access

inside front cover
Grokking Continuous Delivery
Copyright
dedication
brief contents
contents
front matter
forewordsprefaceacknowledgmentsabout this bookWho should read this bookHow this book is organized: A road mapliveBook discussion forumAbout the author
Part 1. Introducing continuous delivery
1 Welcome to Grokking Continuous Delivery
Do you need continuous delivery?Why continuous delivery?Continuous deliveryIntegrationContinuous integrationWhat do we deliver?DeliveryContinuous delivery/deploymentElements of continuous deliveryConclusionSummaryUp next . . .
2 A basic pipeline
Cat Picture WebsiteCat Picture Website source codeCat Picture Website pipelinesWhat’s a pipeline? What’s a task?The basic tasks in a CD pipelineGates and transformationsCD: Gates and transformationsCat Picture Website service pipelineRunning the pipelineRunning once a dayTrying continuous integrationUsing notificationsScaling manual effortAutomation with webhooksScaling with webhooksDon’t push changes when brokenCat Picture Website CDWhat’s in a name?ConclusionSummaryUp next . . .

Part 2. Keeping software in a deliverable state at all times
3 Version control is the only way to roll
Sasha and Sarah’s start-upAll kinds of dataSource and softwareRepositories and versionsContinuous delivery and version controlGit and GitHubAn initial commit—with a bug!Breaking mainPushing and pullingAre we doing continuous delivery?Keep version control releasableTrigger on changes to version controlTriggering the User service pipelineBuilding the User serviceThe User service in the cloudConnecting to the RandomCloud databaseManaging the User serviceThe User service outageOutsmarted by automationWhat’s the source of truth?User service config as codeConfiguring DeployakerConfig as codeRolling out software and config changesConclusionSummaryUp next . . .
4 Use linting effectively
Becky and Super Game ConsoleLinting to the rescue!The lowdown on lintingThe tale of Pylint and many, many issuesLegacy code: Using a systematic approachStep 1: Configure against coding standardsStep 2: Establish a baselineStep 3: Enforce at submission timeAdding enforcement to the pipelineStep 4: Divide and conquerIsolation: Not everything should be fixedEnforcing isolationNot all problems are created equalTypes of linting issuesBugs first, style laterJumping through the hoopsConclusionSummaryUp next . . .
5 Dealing with noisy tests
Continuous delivery and testsIce Cream for All outageSignal vs. noiseNoisy successesHow failures become noiseGoing from noise to signalGetting to greenAnother outage!Passing tests can be noisyFixing test failuresWays of failing: FlakesReacting to failuresFixing the test: Change the code or the test?The dangers of retriesRetrying revisitedWhy do we retry?Get to green and stay greenConclusionSummaryUp next . . .
6 Speeding up slow test suites
Dog Picture WebsiteWhen simple is too simpleNew engineer tries to submit codeTests and continuous deliveryDiagnosis: Too slowThe test pyramidFast tests firstTwo pipelinesGetting the right balanceChanging the pyramidSafely adjusting testsTest CoverageEnforcing test coverageTest coverage in the pipelineMoving tests in the pyramid with coverageWhat to move down the pyramid?Legacy tests and FUDRunning tests in parallelWhen can tests run in parallel?Updating the pipelinesStill too slow!Test sharding, aka parallel++How to shardMore complex shardingSharded pipelineSharding the browser testsSharding in the pipelineDog Picture Website’s pipelinesConclusionSummaryUp next . . .
7 Give the right signals at the right times
CoinExCompareLife cycle of a changeCI only before mergeTimeline of a change’s bugsCI only before merging misses bugsA tale of two graphs: Default to seven daysA tale of two graphs: Default to 30 daysConflicts aren’t always caughtWhat about the unit tests?PR triggering still lets bugs sneak inCI before AND after mergeOption 1: Run CI periodicallyOption 1: Setting up periodic CIOption 2: Require branches to be up-to-dateOption 2: At what cost?Option 3: Automated merge CIOption 3: Running CI with the latest mainOption 3: Merge eventsOption 3: Merge queuesOption 3: Merge queue for CoinExCompareWhere can bugs still happen?Flakes and PR-triggered CICatching flakes with periodic testsBugs and buildingCI vs. build and deployBuild and deploy with the same logicImproved CI pipeline with buildingTimeline of a change revisitedConclusionSummaryUp next . . .
Part 3. Making delivery easy
8 Easy delivery starts with version control
Meanwhile at Watch Me WatchThe DORA metricsVelocity at Watch Me WatchLead time for changesWatch Me Watch and elite performersIncreasing velocity at Watch Me WatchIntegrating with AllCatsAllTheTimeIncremental feature deliveryCommitting skipped testsCode review and “incomplete” codeKeeping up the momentumCommitting work-in-progress codeReviewing work-in-progress codeMeanwhile, back at the end-to-end testsSeeing the benefitsDecreasing lead time for changesContinuing AllCatsAllTheTimeDeployment windows and code freezesIncreased velocityConclusionSummaryUp next . . .
9 Building securely and reliably
Top Dog MapsWhen the build process is a docAttributes of secure and reliable buildsAlways releasableAutomated buildsBuild as codeUse a CD serviceEphemeral build environmentsMiguel’s planFrom a doc to a script in version controlAutomated containerized buildsSecure and reliable build processInterface changes and bugsWhen builds cause bugsBuilds and communicationSemantic versioningThe importance of being versionedAnother outage!Build-time dependency bugsPinning dependenciesVersion pinning alone isn’t a guaranteePinning to hashesConclusionSummaryUp next . . .
10 Deploying confidently
Plenty of deployment woesDORA metrics for stabilityDORA metrics at Plenty of WoofsDeploying less frequently?Deploying more frequently?Daily deployments vs. outagesSteps toward increasing frequencyFixing problems with the processRolling updatesFixing a bug with a rolling updateRollbacksRollback strategy = immediate improvementRollback policy in actionBlue-green deploymentsFaster time to restore with blue-greenFaster and more stable with canariesRequirements for canary deploymentsCanary deployments with baselinesTime to restore with canary deploymentsIncreasing deployment frequencyDORA metrics with daily canary deploymentsContinuous deploymentWhen to use continuous deploymentMandatory QA phasesQA and continuous deploymentElite DORA performanceConclusionSummaryUp next . . .
Part 4. CD design
11 Starter packs: From zero to CD
Starter packs: OverviewRecap: Universal CD pipeline tasksPrototypical release pipelinePrototypical CI pipelineBoth pipelines with triggeringGreenfield: Getting to CDGulpyGreenfield: Zero to CDFirst step: Does it build?Picking a CD systemSetting up the initial automationState of the code: LintingState of the code: Unit testsState of the code: CoverageMoving past CI: PublishingDeploymentExpanding testingTasks for integration and end-to-end testsCompleting the CI pipelineGulpy’s complete pipelinesLegacy: Getting to CDRebellious HamsterFirst step: Prioritize incremental goalsFocusing on the pain firstPain at Rebellious HamsterKnow when things are brokenIsolate and add testsLegacy pipeline with more testsMake deployments more automatedCreating a release pipelineRebellious Hamster’s release pipelineRebellious Hamster’s complete pipelinesConclusionSummaryUp next . . .
12 Scripts are code, too
Purrfect BankCD problemsPurrfect Bank CD overviewPayment Org’s bash librariesTransaction service pipelineEvolving from one big scriptPrinciples of well-designed tasksBreaking up the giant taskUpdated Transaction service pipelineDebugging bash librariesInvestigating the bash library bugWhy was the bug introduced?What is bash for?When is bash less good?Shell scripting vs. general-purpose languagesShell script to general-purpose languageMigration planFrom bash library to task with bashReusable bash inside a taskFrom bash to PythonTasks as codeCD scripts are code, tooConclusionSummaryUp next . . .
13 Pipeline design
PetMatchMatchmaking CD pipelinesCD pipeline problemsEnd-to-end test pipelineEnd-to-end test pipeline and errorsFinally behaviorFinally as a graphFinally in the matchmaking pipelineEnd-to-end test pipeline and speedParallel execution of tasksEnd-to-end test pipeline and test speedParallel execution and test shardingEnd-to-end test pipeline with shardingEnd-to-end test pipeline and signalOne CI pipelineRelease pipeline and signalDifferences in CICombining pipelinesRelease pipelineHardcoding in the release pipelinePipeline reuse with parameterizationUsing reusable pipelinesUpdated pipelinesSolving PetMatch’s CD problemsCD features to look forConclusionSummaryUp next . . .
Appendices
Appendix A. CD systems
CD System features by chapterFeature listArgo WorkflowsCircleCIGitHub ActionsGoogle Cloud BuildJenkins PipelineTekton
Appendix B. Version control systems
Version control systemsHosted version controlFeature listBitbucketGitHubGitLab
index
inside back cover

Content preview from Grokking Continuous Delivery

brief contents

Part 1. Introducing continuous delivery

1 Welcome to Grokking Continuous Delivery

2 A basic pipeline

Part 2. Keeping software in a deliverable state at all times

3 Version control is the only way to roll

4 Use linting effectively

5 Dealing with noisy tests

6 Speeding up slow test suites

7 Give the right signals at the right times

Part 3. Making delivery easy

8 Easy delivery starts with version control

9 Building securely and reliably

10 Deploying confidently

Part 4. CD design

11 Starter packs: From zero to CD

12 Scripts are code, too

13 Pipeline design

Appendices:

Appendix A. CD systems

Appendix B. Version control systems

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781617298257Publisher Support Publisher Website Errata Page

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Grokking Continuous Delivery

by Christie Wilson

brief contents

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.