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