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

Size: px

Start display at page:

Download "WE THOUGHT WE WERE DOING CONTINUOUS DELIVERY AND THEN. Aravind and Suzie ThoughtWorks"

Winfred McCormick
6 years ago
Views:

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

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

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

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

6 WHAT IS CD?

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

8 Do we need this? CONTINUOUS DELIVERY

11 Deliver becom RELEASE RELEASE RELEASE RELEASE YEAR

12 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

13 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

14 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

15 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

16 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

17 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

18 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

19 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

20 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

25 RELEASE RELEASE RELEASE RELEASE YEAR

26 RELEASE 25% RELEASE TIME WAS INSTALLER TESTING RELEASE RELEASE RELEASE YEAR

27 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

28 Commit Build and Test Automated Tests Staging User Acceptance Installer Tests Deliver

29 Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance

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

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

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

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

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

35 RELEASE RELEASE RELEASE RELEASE YEAR

36 Deliver becom RELEASE <5% RELEASE TIME WAS INSTALLER TESTING RELEASE RELEASE RELEASE YEAR

37 HIDDEN SILOS

38 Commit Build and Test Automated Tests Installer Tests Staging Deliver User Acceptance

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

40 LEARNINGS Automate, automate, automate Look for hidden silos

43 Before going open-source

44 DEV & TEST DEV & TEST REGRESSION REGRESSION YEAR 3 to 4 month release cycle

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

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

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

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

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

51 DEV & TEST Regression is just a small buffer now Automated installer tests Automated performance tests (in progress) Automated release note generation Automated publishing of releases Regularly a month, not decided by regression cycle

52 DEV & TEST DEV & TEST DEV & TEST DEV & TEST DEV & TEST Automated installer tests Automated performance tests (in progress) Automated release note generation Automated publishing of releases Release Release Release Release

53 LEARNINGS Frequency reduces difficulty Automation costs pay for themselves

57 Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines GOOD JOB!

58 Continuous Delivery is the ability to get changes of all How do we d -Suzanne Image from Pri b -Suzanne Pri 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.

59 Continuous Delivery is the ability to get changes of all How do we d -Suzanne Image from Pri b -Suzanne Pri 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

60 Continuous Delivery is the ability to get changes of all How do we d -Suzanne Image from Pri b -Suzanne Pri 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

61 Continuous Delivery is the ability to get changes of all How do we d -Suzanne Image from Pri b -Suzanne Pri 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

62 Continuous Delivery is the ability to get changes of all How do we d -Suzanne Image from Pri b -Suzanne Pri 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

63 Microservices RabbitMQ Nagios Automated infrastructure Deployment pipelines

64 Microservices

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

71 TAKE AWAYS

72 PRACTICE CONTINUOUS INTEGRATION

73 FREQUENCY REDUCES DIFFICULTY

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

75 I feel like I want to remove this one. Or at least not have it at the end. Maybe we need a CD is a journey slide? INVOLVE THE WHOLE TEAM

76 AUTOMATE EVERYTHING

77 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

How Can Testing Teams Play a Key Role in DevOps Adoption?

June 3, 2016 How Can Testing Teams Play a Key Role in DevOps Adoption? Sujay Honnamane QA Director @sujayh Rameshkumar Bar Sr. Automation Architect @rameshbar 2016 Cognizant Session take away DevOps Overview