Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
27 lines (21 sloc) 1.77 KB
layout title description date author keywords categories index-image-url index-image-alt
Continuous Delivery is not a destination
Continuous Delivery is a journey, not a destination. Listen to Badri and Akshay discuss this topic from the Pipeline Conference.
Jen Marley
ci tool, ci software, delivery software, continuous delivery, ci automation, continuous delivery tool, continuous integration, what is continuous delivery, snap ci
Pipeline - The Continous Delivery Conference
<iframe src='' frameborder='0' webkitAllowFullScreen="true" mozallowfullscreen="true" allowFullScreen="true"> </iframe>

Snap's product owner Badri Janakiraman and developer Akshay Karle were at the Pipelines annual conference last month, talking about why continuous delivery should be a journey, not a destination. Although it certainly would be easier if one could just do step 1, step 2, etc, and achieve continuous delivery, it's more complex than that and really should be a set of principles that informs tool choices, systems architecture, and development practices. Here are a few key points from the talk:

  • Start with getting working software into hands of users
  • Don’t be afraid of “re-design”/”re-work”
  • Layer on qualities of reliability, automation, frequent releases, etc.
  • Kick the can down the road.

You can watch the video below and download the slides from the talk here.

Snap CI © 2017, ThoughtWorks

You can’t perform that action at this time.