Successfully reported this slideshow.
Your SlideShare is downloading. ×

We thought we were doing continuous delivery and then...

Ad

WE THOUGHT WE WERE
DOING CONTINUOUS
DELIVERY AND THEN…
Aravind and Suzie 

ThoughtWorks

Ad

Define Continuous Delivery (CD)

Tell some stories :)

Review learnings and share tips
WHAT WE WILL COVER

Ad

Aravind SV (“Duck”)
Product Manager for GoCD
10+ years of helping different
clients with Agile/XP, CI and CD
practices
Twe...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Loading in …3
×

Check these out next

1 of 85 Ad
1 of 85 Ad

We thought we were doing continuous delivery and then...

Download to read offline

Are you sure you are doing continuous delivery? Yeah right! We thought we were too. The journey to continuous delivery (CD) is long, winding and always evolving. Like with many things we thought we had achieved all we could with continuous delivery and then... our business model changed, and then...

Originally presented at QCon New York June 2016 https://qconnewyork.com/ny2016/ny2016/presentation/we-thought-we-were-doing-continuous-delivery-and-then.html

Are you sure you are doing continuous delivery? Yeah right! We thought we were too. The journey to continuous delivery (CD) is long, winding and always evolving. Like with many things we thought we had achieved all we could with continuous delivery and then... our business model changed, and then...

Originally presented at QCon New York June 2016 https://qconnewyork.com/ny2016/ny2016/presentation/we-thought-we-were-doing-continuous-delivery-and-then.html

Advertisement
Advertisement

More Related Content

Slideshows for you (19)

Advertisement

Similar to We thought we were doing continuous delivery and then... (20)

Advertisement

We thought we were doing continuous delivery and then...

  1. 1. WE THOUGHT WE WERE DOING CONTINUOUS DELIVERY AND THEN… Aravind and Suzie ThoughtWorks
  2. 2. Define Continuous Delivery (CD) Tell some stories :) Review learnings and share tips WHAT WE WILL COVER
  3. 3. Aravind SV (“Duck”) Product Manager for GoCD 10+ years of helping different clients with Agile/XP, CI and CD practices Tweeting from @arvindsv
  4. 4. Suzie Prince Head of Product for ThoughtWorks products group Product Manager for Snap CI 10 + years experience with agile including CI and CD practices Tweeting @pm_suzie
  5. 5. WHAT IS CD?
  6. 6. “Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.”
  7. 7. CONTINUOUS DELIVERY
  8. 8. RELEASE RELEASE RELEASE RELEASE YEAR
  9. 9. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  10. 10. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  11. 11. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  12. 12. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  13. 13. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  14. 14. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  15. 15. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  16. 16. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  17. 17. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  18. 18. RELEASE YEAR RELEASE RELEASE RELEASE
  19. 19. RELEASE RELEASE RELEASE RELEASE YEAR 25% RELEASE TIME WAS INSTALLER TESTING
  20. 20. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  21. 21. Commit Build and Test Automated Tests Installer TestsStaging Deliver User Acceptance
  22. 22. Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  23. 23. Commit Build and Test Automated Tests Staging Deliver User Acceptance Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  24. 24. Commit Build and Test Automated Tests Staging Deliver User Acceptance Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  25. 25. Commit Build and Test Automated Tests Staging Deliver User Acceptance Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  26. 26. Commit Build and Test Automated Tests Staging Deliver User Acceptance Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  27. 27. Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  28. 28. RELEASE RELEASE RELEASE RELEASE YEAR
  29. 29. RELEASE RELEASE RELEASE YEAR RELEASE <5% RELEASE TIME WAS INSTALLER TESTING
  30. 30. HIDDEN SILOS
  31. 31. Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  32. 32. Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance
  33. 33. LEARNINGS Automate, automate, automate Look for hidden silos
  34. 34. Before going open-source …
  35. 35. DEV & TEST REGRESSION 3 to 4 month release cycle DEV & TEST REGRESSION YEAR
  36. 36. DEV & TEST REGRESSION INSTALLER TESTS WRITE RELEASE NOTES PERFORMANCE TESTS UPLOAD/PUBLISH INSTALLERS 1 to 1.5 months
  37. 37. DEV & TEST REGRESSION INSTALLER TESTS WRITE RELEASE NOTES PERFORMANCE TESTS 1 to 1.5 months Automated publishing of releases
  38. 38. DEV & TEST REGRESSION WRITE RELEASE NOTES PERFORMANCE TESTS 1 to 1.5 months Automated publishing of releases Automated installer tests
  39. 39. DEV & TEST REGRESSION PERFORMANCE TESTS 1 to 1.5 months Automated publishing of releases Automated installer tests Automated release note generation
  40. 40. DEV & TEST 1 to 1.5 months Automated publishing of releases Automated installer tests Automated release note generation Automated performance tests (in progress) REGRESSION
  41. 41. DEV & TEST Regularly a month, not decided by regression cycle Automated publishing of releases Automated installer tests Automated release note generation Automated performance tests (in progress) Regression is just a small buffer now
  42. 42. DEV & TEST Automated publishing of releases Automated installer tests Automated release note generation Automated performance tests (in progress) DEV & TEST DEV & TEST DEV & TEST DEV & TEST ReleaseRelease Release Release
  43. 43. LEARNINGS Frequency reduces difficulty Automation costs pay for themselves
  44. 44. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines
  45. 45. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines
  46. 46. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines
  47. 47. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines
  48. 48. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines
  49. 49. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines
  50. 50. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines GOOD JOB!
  51. 51. “Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.”
  52. 52. “Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way
  53. 53. “Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way
  54. 54. “Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way
  55. 55. “Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way
  56. 56. Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines
  57. 57. Microservices
  58. 58. LEARNINGS Delivering value, not doing CD is your job CD is a journey
  59. 59. TAKE AWAYS
  60. 60. PRACTICE CONTINUOUS INTEGRATION
  61. 61. FREQUENCY REDUCES DIFFICULTY
  62. 62. DOING CONTINUOUS DELIVERY IS NOT YOUR JOB Microservices Chef Server RabbitMQ Nagios Automated infrastructure Deployment pipelines
  63. 63. INVOLVE THE WHOLE TEAM
  64. 64. AUTOMATE EVERYTHING
  65. 65. PARTING THOUGHTS… You will look back on what you did later and see how it could have been better Focus on what is not good now and improve that Don’t be too critical but know that where you are right now is not the best place you could be Don’t fear redesign, don’t fear rework, you’ll end up doing it anyway

×