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

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

2. Define Continuous Delivery (CD)
Tell some stories :)
Review learnings and share tips
WHAT WE WILL COVER

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. 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

7. WHAT IS CD?

8. “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.”

9. CONTINUOUS DELIVERY

12. RELEASE
RELEASE
RELEASE
RELEASE
YEAR

13. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

14. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

15. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

16. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

17. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

18. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

19. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

20. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

21. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

26. RELEASE
YEAR
RELEASE
RELEASE
RELEASE

27. RELEASE
RELEASE
RELEASE
RELEASE
YEAR
25% RELEASE TIME WAS
INSTALLER TESTING

28. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

29. Commit Build and Test
Automated
Tests
Installer TestsStaging Deliver
User
Acceptance

30. Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

31. Commit Build and Test
Automated
Tests
Staging Deliver
User
Acceptance
Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

32. Commit Build and Test
Automated
Tests
Staging Deliver
User
Acceptance
Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

33. Commit Build and Test
Automated
Tests
Staging Deliver
User
Acceptance
Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

34. Commit Build and Test
Automated
Tests
Staging Deliver
User
Acceptance
Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

35. Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

36. RELEASE
RELEASE
RELEASE
RELEASE
YEAR

37. RELEASE
RELEASE
RELEASE
YEAR
RELEASE
<5% RELEASE TIME WAS
INSTALLER TESTING

38. HIDDEN SILOS

39. Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

40. Commit Build and Test
Automated
Tests
Installer Tests Staging Deliver
User
Acceptance

41. LEARNINGS
Automate, automate, automate
Look for hidden silos

44. Before going open-source …

45. DEV & TEST
REGRESSION
3 to 4 month release cycle
DEV & TEST
REGRESSION
YEAR

47. DEV & TEST
REGRESSION
INSTALLER TESTS
WRITE RELEASE NOTES
PERFORMANCE TESTS
UPLOAD/PUBLISH INSTALLERS
1 to 1.5 months

48. DEV & TEST
REGRESSION
INSTALLER TESTS
WRITE RELEASE NOTES
PERFORMANCE TESTS
1 to 1.5 months
Automated publishing of releases

49. DEV & TEST
REGRESSION
WRITE RELEASE NOTES
PERFORMANCE TESTS
1 to 1.5 months
Automated publishing of releases
Automated installer tests

50. DEV & TEST
REGRESSION
PERFORMANCE TESTS
1 to 1.5 months
Automated publishing of releases
Automated installer tests
Automated release note generation

51. DEV & TEST
1 to 1.5 months
Automated publishing of releases
Automated installer tests
Automated release note generation
Automated performance tests (in progress)
REGRESSION

52. 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

53. 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

54. LEARNINGS
Frequency reduces difficulty
Automation costs pay for themselves

58. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

59. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

60. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

61. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

62. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

63. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

64. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines
GOOD JOB!

65. “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.”

66. “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

67. “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

68. “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

69. “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

70. Microservices
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

71. Microservices

78. LEARNINGS
Delivering value, not doing CD is your job
CD is a journey

79. TAKE AWAYS

80. PRACTICE CONTINUOUS INTEGRATION

81. FREQUENCY REDUCES DIFFICULTY

82. DOING CONTINUOUS DELIVERY IS NOT YOUR JOB
Microservices
Chef Server
RabbitMQ
Nagios
Automated infrastructure
Deployment pipelines

83. INVOLVE THE WHOLE TEAM

84. AUTOMATE EVERYTHING

85. 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