evolving continuous delivery
play

Evolving Continuous Delivery Chris Read @cread - PowerPoint PPT Presentation

Evolving Continuous Delivery Chris Read @cread http://chris-read.net Wednesday, 11 May 2011 1 What Were Told @cread http://chris-read.net Wednesday, 11 May 2011 2 What Were Told Single Source Repository @cread


  1. Evolving Continuous Delivery Chris Read @cread http://chris-read.net Wednesday, 11 May 2011 1

  2. What We’re Told @cread http://chris-read.net Wednesday, 11 May 2011 2

  3. What We’re Told • Single Source Repository @cread http://chris-read.net Wednesday, 11 May 2011 3

  4. What We’re Told • Automate Build and Testing @cread http://chris-read.net Wednesday, 11 May 2011 4

  5. What We’re Told • Publish Latest Distributable @cread http://chris-read.net Wednesday, 11 May 2011 5

  6. What We’re Told • Every Commit Builds @cread http://chris-read.net Wednesday, 11 May 2011 6

  7. What We’re Told • Test in Production Like Environment @cread http://chris-read.net Wednesday, 11 May 2011 7

  8. What We’re Told • Keep Builds Fast @cread http://chris-read.net Wednesday, 11 May 2011 8

  9. What We’re Told • Use Information Radiators @cread http://chris-read.net Wednesday, 11 May 2011 9

  10. What We’re Told • Automate Deployment @cread http://chris-read.net Wednesday, 11 May 2011 10

  11. What We’re Told • Build Binary Once @cread http://chris-read.net Wednesday, 11 May 2011 11

  12. What We’re Told • Promote Binary Through Stages @cread http://chris-read.net Wednesday, 11 May 2011 12

  13. Evolution @cread http://chris-read.net Wednesday, 11 May 2011 13

  14. Initial State • New team of talented and impatient developers • Starting to create trading applications for an established desk @cread http://chris-read.net Wednesday, 11 May 2011 14

  15. Initial State • Releasing daily from developer workstations to production • No Continuous Integration! • Using Fig for dependency management @cread http://chris-read.net Wednesday, 11 May 2011 15

  16. Stage I • Standardise and Refactor the build scripts • Add Continuous Integration server • Set up an Information Radiator @cread http://chris-read.net Wednesday, 11 May 2011 16

  17. Stage II • Create a standard deployment script • Turn the scripts into dependencies • Try a different CI server @cread http://chris-read.net Wednesday, 11 May 2011 17

  18. Stage III • Sideline the Continuous Integration loop • Bake the Continuous Integration safeties into the deployment scripts @cread http://chris-read.net Wednesday, 11 May 2011 18

  19. Stage IV • Automate server builds • Start to scale services out @cread http://chris-read.net Wednesday, 11 May 2011 19

  20. Stage V • Fracture services out into stacks • Bring the Continuous Integration loop back inline • Stage the binaries @cread http://chris-read.net Wednesday, 11 May 2011 20

  21. What Have I Learned? • The Things We’re Told still hold, but implementation will vary greatly • Constantly re-evaluate your tools and your process - ensure you have the right tool • Always question the return on investment @cread http://chris-read.net Wednesday, 11 May 2011 21

  22. Thank You @cread http://chris-read.net Wednesday, 11 May 2011 22

Recommend


More recommend