A way to continuous delivery

Post on 15-Jul-2015

479 views 1 download

Tags:

Transcript of A way to continuous delivery

A way to continuous delivery

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

Continuous integration, delivery

& deployment

Terms

• Continuous integration

• Continuous delivery

• Continuous deployment

Scrum & Continuous

Delivery

Where I’m coming from

Background

Web tools for professionals.

• 50/50 designer/developer

• Ruby on Rails

• SaaS & PaaS

• Partner of the company

• Keep the technology side of our projects excellent

Our path to continuous delivery

From Nebula to Heroku

Continuous integration server

Alerting

Monitoring

• Automation

• Everything under version control

• Hosted platforms

• Open-source

• Cross-service integration

• Visibility

Pain

• Don't brush it off

• Listen to your pain

• Let it guide you

"... broke again!"

"Why do we always ...?"

"I waste time on this on every project"

• 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

• 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

Future

"The future is already here

— it's just not very evenly

distributed."

• Need for faster feedback, confidence and predictability is always there

• Tools are ge#ing be#er everywhere

• For us: automatic deployment to staging

• 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

• Cultures will change

• From Hollywood launches to more incremental and iterative approach

• Feature flags, stealth launches, deploying the backend first…

TODO

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

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

Thank you!

Email: vesa@kiskolabs.com Twi!er: @vesan