35
A way to continuous delivery Continuous delivery seminar 2.12.2014 Vesa Vänskä, Kisko Labs

A way to continuous delivery

Embed Size (px)

Citation preview

Page 1: A way to continuous delivery

A way to continuous delivery

Continuous delivery seminar 2.12.2014 Vesa Vänskä, Kisko Labs

Page 2: A way to continuous delivery

Continuous integration, delivery

& deployment

Terms

Page 3: A way to continuous delivery

• Continuous integration

• Continuous delivery

• Continuous deployment

Page 4: A way to continuous delivery

Scrum & Continuous

Delivery

Page 5: A way to continuous delivery

Where I’m coming from

Background

Page 6: A way to continuous delivery

Web tools for professionals.

Page 7: A way to continuous delivery

• 50/50 designer/developer

• Ruby on Rails

• SaaS & PaaS

Page 8: A way to continuous delivery

• Partner of the company

• Keep the technology side of our projects excellent

Page 9: A way to continuous delivery

Our path to continuous delivery

Page 10: A way to continuous delivery
Page 11: A way to continuous delivery

From Nebula to Heroku

Page 12: A way to continuous delivery
Page 13: A way to continuous delivery

Continuous integration server

Page 14: A way to continuous delivery
Page 15: A way to continuous delivery

Alerting

Page 16: A way to continuous delivery

Monitoring

Page 17: A way to continuous delivery
Page 18: A way to continuous delivery
Page 19: A way to continuous delivery

• Automation

• Everything under version control

• Hosted platforms

• Open-source

• Cross-service integration

• Visibility

Page 20: A way to continuous delivery

Pain

Page 21: A way to continuous delivery

• Don't brush it off

• Listen to your pain

• Let it guide you

Page 22: A way to continuous delivery

"... broke again!"

Page 23: A way to continuous delivery

"Why do we always ...?"

Page 24: A way to continuous delivery

"I waste time on this on every project"

Page 25: A way to continuous delivery

• 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

• 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

Future

Page 28: A way to continuous delivery

"The future is already here

— it's just not very evenly

distributed."

Page 29: A way to continuous delivery

• 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

• 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

• 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

TODO

Page 33: A way to continuous delivery

• 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?

Page 34: A way to continuous delivery

h#p://martinfowler.com/delivery.html

Page 35: A way to continuous delivery

Thank you!

Email: [email protected] Twi!er: @vesan