Demystifying DevOps and CI/CD

Image credit: https://github.com/infrabricks/wordcloud

Jeremy Meiss DevRel & Community leader Open to work jmeiss.me

What is DevOps?

“Ok blue-haired dude, what really is DevOps and where did it come from?”

1910s to 1930s “Flow production”

1990s

“10+ Deploys per Day: Dev and Ops Cooperation at Flickr” - John Allspaw, Paul Hammond

Image credit: freepik

MAY 15-16, 2024 devopsdayskc.org

Image credit: ROELBOB at DevOps.com

Imagine you’re getting ready to ship something…

You press the big red button

click

silence

Do you… a) Sweat and wait to see if it blows up

Do you… a) Sweat and wait to see if it blows up b) Pack up, go home & enjoy your weekend

It all boils down to automation.

Image source: Horizon Zero Dawn

Image source: Demotivational

Continuous {Integration|Deployment}

CI == Continuous Integration the practice of merging all developers’ working copies to a shared code repository Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website

CD == Continuous Deployment the practice of automatically deploying new software releases to target environments Build Website Server deployment Active Users

Scrumban!

Quick History of CI/CD 1991

Quick History of CI/CD 1991 1997

Quick History of CI/CD 2001 1991 1997

Quick History of CI/CD

Quick History of CI/CD AWS CodePipeline GitHub Actions

Software Development without CI/CD

Software Development without CI/CD Image source: Oursky

CI == Continuous Integration the practice of merging all developers’ working copies to a shared code repository Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website

CI == Continuous Integration ● Every developer commits daily+ to shared mainline code repo Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website

CI == Continuous Integration ● ● Every developer commits daily+ to shared mainline code repo Every commit triggers automated build and test of the codebase Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website

CI == Continuous Integration ● ● ● Every developer commits daily+ to shared mainline code repo Every commit triggers automated build and test of the codebase If the build or any test fails, it’s repaired quickly – often within minutes Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website

CI == Continuous Integration ● ● ● ● Every developer commits daily+ to shared mainline code repo Every commit triggers automated build and test of the codebase If the build or any test fails, it’s repaired quickly – often within minutes Only integrate tested code into code base Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website

CI == Continuous Integration ● ● ● ● ● Every developer commits daily+ to shared mainline code repo Every commit triggers automated build and test of the codebase If the build or any test fails, it’s repaired quickly – often within minutes Only integrate tested code into code base Changes frequently merged into release branches Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website

Image credit: Product Coalition

Image credit: Giphy

CD == Continuous Deployment the practice of automatically deploying new software releases to target environments Build Website Server deployment Active Users

CD == Continuous Deployment ● Build Website Faster release cycles Server Deployment Active Users

CD == Continuous Deployment ● ● Build Website Faster release cycles Low-risk releases Server Deployment Active Users

CD == Continuous Deployment ● ● ● Build Website Faster release cycles Low-risk releases Higher quality Server Deployment Active Users

CD == Continuous Deployment ● ● ● ● Build Website Faster release cycles Low-risk releases Higher quality Lower costs Server Deployment Active Users

CI vs CD(elivery) vs CD(eployment)?

Implementing CI/CD

Image credit: Giphy

Make sure everyone is on the same page

Always start small

Do what works for you

Always measure

95% 50% Image credit: Giphy

CI/CD Benchmarks Throughput Duration At will <10 minutes Success Rate

90% Mean Time to Recovery <1 hour

Streamline deploy

Thank you. IAmJerdog jerdog /in/jeremymeiss jerdog@hachyderm.io