It’s Not Continuous Delivery If You Can’t Deploy Right Now • Ken Mugrage • GOTO 2017

This presentation was recorded at GOTO Amsterdam 2017. #GOTOcon #GOTOams
gotoams.nl
Ken Mugrage - Technology Evangelist with ThoughtWorks
ABSTRACT
I hear people say all the time that they're practicing continuous delivery. This declaration is often followed by something like, "I can let the security team know anytime", or "I just have to run the performance tests". If you can't push your software [...]
Download slides and read the full abstract here:
gotoams.nl/2017/sessions/214
/ gotoamst
/ gotoconference
gotocon.com
#ContinuousDelivery #CD #DeployNow #DeliveryPipelines #DeploymentPatterns
Looking for a unique learning experience?
Attend the next GOTO Conference near you! Get your ticket at gotocon.com
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
kzbin.info...

[@andrealaforgia]

Fantastic talk!

[@bguen1234]

This talk is spot on. "Aim small, miss small" If you require devs to push code that builds every day it forces them to "Aim small". There are very few days in the last 15 years that we couldn't push to production that day if we needed to. Don't concentrate on building Lego castles, concentrate on building Lego blocks. That way when the folks that write the checks decide the Lego castle was supposed to be a Lego skyscraper you can just roll with it.

[@dmlled]

nice patterns from the big VSM example. Can relate to the decisions and trade-offs

[@bobbymann2225]

I liked this alot! thanks

[@drabiu]

When you have teams divided into separate domains feature branching won't cause massive conflicts so it won't be a problem in continuous delivery

[@kevinfleischer2049]

If you have this, why go through the hassle of deploying it together. Make it separate products and deploy them separately.

[@lepidoptera9337]

It is never "continuous delivery" for a serious software product. You can't ship a CAD tool with 30% functionality and expect that people will pay money. Either everything works on day one or you don't have a product.

[@srikanth4u192]

I wish there were more examples on some of the openions...

[@srikanth4u192]

Don't completely agree about rollbacks, roll back makes things faster and safer only challenge is identifing the culprit and collaratels ....

[@RobertKraig]

You merge to master, you develop on a topic branch of master. Your changes have a CI pipeline on topic branches. the CD is when master receives a merge. It should never reach master unless it's passing the CI pipeline 1st, pushing to master always is cow-boying it. So the only way to prevent failure is to avoid pushing broken code into master. Master should never break, period, full stop.

[@erikkalkoken3494]

If you wonder what the $ amount on the slides is all about. Wait until the end .....

[@YTPrule]

According to Reddit www.reddit.com/r/programming/comments/b3c8wq/its_not_continuous_delivery_if_you_cant_deploy/, this video should be ignored.

[@BryonLape]

There is no such thing as the Agile Manifesto.

[@rexsheridan5534]

Not sure what you mean. agilemanifesto.org/

[@renxula]

He's probably referring to what e.g. Dave Thomas said: "agile" is an adjective, and using it as a noun like "I'm doing agile" is silly. The manifesto isn't agile. The name of the document is "Manifesto for Agile Software Development". Though yeah, that domain name does kind of go against his point :) But another point was that agile as a noun has become somewhat of a curse word, something that training and certification companies sell, while falling short of the true ideas behind the manifesto, which are still valid today.

[@tr233]

This man is crazy he would be fired, when he did worked in enterprise area.

[@davidjulitz7446]

Thats why "classic" enterprises fail to keep their software secure and performant and often disappoint end users on a regular base.