a way to continuous delivery
TRANSCRIPT
![Page 1: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/1.jpg)
A way to continuous delivery
Continuous delivery seminar 2.12.2014 Vesa Vänskä, Kisko Labs
![Page 2: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/2.jpg)
Continuous integration, delivery
& deployment
Terms
![Page 3: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/3.jpg)
• Continuous integration
• Continuous delivery
• Continuous deployment
![Page 4: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/4.jpg)
Scrum & Continuous
Delivery
![Page 5: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/5.jpg)
Where I’m coming from
Background
![Page 6: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/6.jpg)
Web tools for professionals.
![Page 7: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/7.jpg)
• 50/50 designer/developer
• Ruby on Rails
• SaaS & PaaS
![Page 8: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/8.jpg)
• Partner of the company
• Keep the technology side of our projects excellent
![Page 9: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/9.jpg)
Our path to continuous delivery
![Page 10: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/10.jpg)
![Page 11: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/11.jpg)
From Nebula to Heroku
![Page 12: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/12.jpg)
![Page 13: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/13.jpg)
Continuous integration server
![Page 14: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/14.jpg)
![Page 15: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/15.jpg)
Alerting
![Page 16: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/16.jpg)
Monitoring
![Page 17: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/17.jpg)
![Page 18: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/18.jpg)
![Page 19: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/19.jpg)
• Automation
• Everything under version control
• Hosted platforms
• Open-source
• Cross-service integration
• Visibility
![Page 20: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/20.jpg)
Pain
![Page 21: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/21.jpg)
• Don't brush it off
• Listen to your pain
• Let it guide you
![Page 22: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/22.jpg)
"... broke again!"
![Page 23: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/23.jpg)
"Why do we always ...?"
![Page 24: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/24.jpg)
"I waste time on this on every project"
![Page 25: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/25.jpg)
• A"er you've become conscious of the painyou can try to remove the source of it
• Learning new techniques, languages and toolsmakes you discover new pains
• Life will never be pain free so why not use it as a valuable tool
![Page 26: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/26.jpg)
• Heroku was relief to the pain of not having automated server administration
• Monitoring was relief to the pain of not having visibility
• Moving alerting from email to a centralized system was also relief to the lack of visibility
• Continuous integration server was the relief for not having certainty
![Page 27: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/27.jpg)
Future
![Page 28: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/28.jpg)
"The future is already here
— it's just not very evenly
distributed."
![Page 29: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/29.jpg)
• Need for faster feedback, confidence and predictability is always there
• Tools are ge#ing be#er everywhere
• For us: automatic deployment to staging
![Page 30: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/30.jpg)
• Currently proprietary platforms are ahead
• Self-hosted and open-source solutions will get there
• I see this as the way most services should be built and run in the future
![Page 31: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/31.jpg)
• Cultures will change
• From Hollywood launches to more incremental and iterative approach
• Feature flags, stealth launches, deploying the backend first…
![Page 32: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/32.jpg)
TODO
![Page 33: A way to continuous delivery](https://reader034.vdocuments.us/reader034/viewer/2022042817/55a63f9f1a28ab3e3a8b4577/html5/thumbnails/33.jpg)
• What is the most painful part of your system and how could your teamminimize that pain?
• Did I talk about a technology or process unknown to you? Take 15 minutes tomorrow and investigate it.
• Is there a blocker for implementing one of the continuous integration practices? Can that be solved?