Continuous Delivery for the rest of us About me Lisa van Gelder - - PowerPoint PPT Presentation

▶
continuous delivery
SMART_READER_LITE
LIVE PREVIEW

Continuous Delivery for the rest of us About me Lisa van Gelder - - PowerPoint PPT Presentation

Apr 12, 2023 103 likes •670 views

Continuous Delivery for the rest of us About me Lisa van Gelder Consultant at Cyrus Innovation lvangelder@cyrusinnovation.com @techbint Continuous Delivery Is not: Continuous deployment Automating all the things Is :

slide-1
SLIDE 1

Continuous Delivery

for the rest of us

slide-2
SLIDE 2

About me

  • Lisa van Gelder
  • Consultant at Cyrus Innovation
  • lvangelder@cyrusinnovation.com
  • @techbint
slide-3
SLIDE 3

Continuous Delivery

Is not:

  • Continuous deployment
  • Automating all the things

Is:

  • Removing the bottlenecks that stop you delivering
slide-4
SLIDE 4
slide-5
SLIDE 5
slide-6
SLIDE 6
slide-7
SLIDE 7
slide-8
SLIDE 8
slide-9
SLIDE 9
slide-10
SLIDE 10
slide-11
SLIDE 11
slide-12
SLIDE 12
slide-13
SLIDE 13
slide-14
SLIDE 14
slide-15
SLIDE 15

Ooda loop

  • observe, orient, decide, and act
  • John Boyd, Father of the F16
slide-16
SLIDE 16
slide-17
SLIDE 17

Continuous Delivery

  • Measure the total cycle time
  • Reduce your cycle time
  • Improve your reaction time
slide-18
SLIDE 18

How do you choose where to start?

slide-19
SLIDE 19

Double the frequency

  • f releases
slide-20
SLIDE 20

Benefits of smaller releases

  • Code only has value in production - get it there

quicker!

  • Less co-ordination required
  • Easier to test
  • Easier to see if it caused issues in production
  • Easier to rollback
slide-21
SLIDE 21

If you can’t release, fake it

slide-22
SLIDE 22
slide-23
SLIDE 23

Blockers

  • Releases cause problems for users
  • Ops team don’t have time to do more releases
  • Ops/dev don’t have time to support more releases
  • QA don’t have time to test new features
  • Takes too long to get a green build
slide-24
SLIDE 24

Releases cause problems for users

  • data loss
  • performance issues
  • broken functionality
slide-25
SLIDE 25

The cms that made journalists stop work for 20 minutes…

  • db changes tied to code changes
  • too much state in session
slide-26
SLIDE 26

Releases cause performance problems

  • play back logs
  • soak test
  • dark launch
  • performance test as soon as you can
slide-27
SLIDE 27

Releases break existing functionality

  • missing tests
  • no env like prod to test on
slide-28
SLIDE 28

The cdn that broke the release

  • POST /myapp/comment/123/recommend
slide-29
SLIDE 29

Ops don’t have the time to perform more releases

slide-30
SLIDE 30
slide-31
SLIDE 31
slide-32
SLIDE 32

Ops/dev don’t have time to watch releases

  • Release interrupts normal work
  • Team on standby in case of issues
slide-33
SLIDE 33

Help!

slide-34
SLIDE 34
slide-35
SLIDE 35

Rollbacks

  • The risk is much higher when rollback isn’t possible
  • Rollbacks should be normal operation, not a failure
  • Users don’t care about your new feature if the site

is down

  • 1. It should be possible to rollback
  • 2. It should be quick to rollback
slide-36
SLIDE 36

Rollbacks

slide-37
SLIDE 37

A release should be a non- event

  • Done in working hours
  • Easy to monitor
  • Easy to rollback
slide-38
SLIDE 38

QA don’t have time to test

slide-39
SLIDE 39
slide-40
SLIDE 40

Cross-functional issues

  • release waiting on qa sign off
  • release waiting on product manager sign off
  • developers waiting on designs
  • ux waiting on developers
  • front-end developers waiting on back-end
slide-41
SLIDE 41
slide-42
SLIDE 42

Cross functional teams

  • don’t start story if all resources aren’t available
  • blockers should block
  • when work is held up - can someone else perform

that function?

slide-43
SLIDE 43

Takes too long to get a green build

  • Flaky tests
  • Slow-running tests
  • Merge hell
slide-44
SLIDE 44

Flaky tests

  • The tests that cry wolf
  • Isolate them
  • Fix them or delete them
slide-45
SLIDE 45

Slow running tests

  • More than 5 minutes is slow
  • Waste of developer time
  • Interrupt flow to fix
  • People deploy without waiting for tests
  • Frequent broken build
slide-46
SLIDE 46

Slow running tests

  • separate unit tests from acceptance tests
  • limit the amount of acceptance tests
  • mock dependencies - limit calls to db
  • run tests in parallel
slide-47
SLIDE 47

Merge hell

  • Continuous Integration is more often than you think!
  • Don’t have long lived feature branches
  • Check in to master at least once a day
  • Feature switches
  • Branch by abstraction
slide-48
SLIDE 48
slide-49
SLIDE 49

QA define automated testing strategy

slide-50
SLIDE 50

Automate performance tests

What criteria do humans use to evaluate performance tests?

slide-51
SLIDE 51
  • Have a performance test environment that is a scaled-

down replica of production

  • Automate log collection, make sure tests reflect current

traffic patterns.

  • Use your application-specific metrics
  • Define acceptable ranges for your application
slide-52
SLIDE 52

Automate release process

What criteria do humans use to evaluate a successful release? Use your application-specific metrics and acceptable ranges

slide-53
SLIDE 53

Summary

  • Measure your cycle time
  • Fix your bottlenecks
  • Improve your reaction time
slide-54
SLIDE 54

Questions?

Feedback please! http://bit.ly/1q3FFIo

slide-55
SLIDE 55

Suggestions for further reading

  • Continuous Delivery by Jez Humble & David Farley
  • The Phoenix Project by Gene Kim, Kevin Behr &

George Spafford

  • The Goal by Eliyahu M. Goldratt & Jeff Cox
  • Lean Software Development by Mary Poppendieck

& Tom Poppendieck

  • Release It! by Michael T. Nygard