What is Continuous Delivery?

Eric Minick with IBM Cloud explains what continuous delivery is and how it’s used to push code to production through a continuous delivery pipeline.

#devops #continuousdelivery #ibmcloud

[alkasingh]

I would like to see more videos from Eric Minick. He explains really well and I understand concept in first watch of the video as a layman.

[quanchi]

Yes, finally a clear explanation of CI and CD. Thanks.

[fabiocinicolo]

This guy explanations are always very clear and concise, would love to see more of him

[syedsaif]

I can't imagine how thorough one must be with these concepts, to explain them in a way that Mr. Minick does. The guy made my jaw drop with his presentation and speaking skills, like DAAMN!

[samueljung]

Love the simple, straight-to-the-point explanation, Eric. Hope to see more of your videos.

[RenStrider]

Meanwhile, I'm already impressed by how well Mr. Minick can nonchalantly write backward while explaining everything so nicely!

[vikstu]

I loved this style on writing in front of the teacher, pretty cool. Very good content also, thank you

[HoldenMadagameTenor]

Another fantastic explanation. Thank you so much for making this so clear. I feel much more prepared to talk intelligently about this.

[asifchoudhuryca]

Watch this short video now to save hours of your time scouring internet watching and reading half-baked, vague materials making you even more confused.

Thanks IBM cloud.

[cedrickiplimo]

Your explanations are easy to follow 👍

[alauddinm]

Thanks for sharing. Awesome explanation of CI/CD for the beginners

[marcotroster]

CD is not about the pipeline itself or any tooling. In fact, the idea is much deeper. Maybe listen to Dave Farley, the co-author of the Continuous Delivery book. He's much better at explaining his idea.

He says you always want the software to be in a releasible state such that it's no longer a technical decision when to deploy. The tests need to give you enough confidence to pull the trigger whenever the pipeline completes successfully. It's a definitive indicator whether the code can be shipped.

Also CD is a work philosophy. You want to make lots of small changes (experiments) and deliver them as fast as possible to gather customer feedback and adapt the product accordingly. The pipeline is just a means to this experimental style of agile software development.

And the CI part is also important. In a proper codebase you'd only have a single branch. This forces devs to work in very small steps and integrate it with all other commits at least once per day. Unfinished code is hidden behind feature flags if necessary. That way you surface other devs changes immediately and don't get crazy merge conflicts. Also there's an emphasis on the latest version because only that version is relevant.

[LOKO]

I loved this video. Thank you for all your insights.

[donaldkennedy]

great explanation of CD for a non programmer ;)

[MrProgguru]

Awesome explanation .. I wonder how you shoot your videos with the glass and pens and the instructor behind it

[goalkickerbooks]

CAB is Change Advisory Board; not Change Approval Board

[awakeupcall]

what difference might be between testing QA and Stage?

[ألفومية-حك]

So Continuous integration is one phase of CD?

[termonasti]

Hi, Automatic test means, unit tests written while coding or test automation ?

[BR-gtzk]

No idea why .. this guy nailed it into my head ..x..l..n..tee