Deploy, Release, CI/CD, Oh My! DevOps for the Rest of us
Slide 1
Slide 2
bit.ly/VueConf2022
Slide 3
Image credit: https://github.com/infrabricks/wordcloud
Slide 4
Slide 5
Jeremy Meiss Director, DevRel & Community timeline.jerdog.me
Slide 6
Image credit: https://github.com/infrabricks/wordcloud
Slide 7
Slide 8
What is DevOps?
Slide 9
Image credit: freepik
Slide 10
Slide 11
Slide 12
Image credit: ROELBOB at DevOps.com
Slide 13
Image credit: ROELBOB at DevOps.com
Slide 14
Image credit: ROELBOB at DevOps.com
Slide 15
AIOps
Slide 16
“AIOps combines big data and machine learning to automate IT operations processes, including event correlation, anomaly detection, and causality determination.” — Gartner
Slide 17
Slide 18
Image credit: Gartner Blog Network
Slide 19
Image credit: Capgemini
Slide 20
GitOps
Slide 21
Slide 22
Slide 23
Ops “GitOps is a way to do Kubernetes cluster management and application delivery… by using Git as a single source of truth for declarative infrastructure and applications.” — Weaveworks
Slide 24
Image credit: VMWare
Slide 25
DevSecOps
Slide 26
“DevSecOps puts security at the forefront of the development process as a whole, ensuring that good cyber-hygiene remains top-of-mind for developers and operators from start to finish.” — Phil Richards Source: Threatpost
Slide 27
“an augmentation of DevOps to allow for security practices to be integrated into the DevOps approach… Each delivery team is empowered to factor in the correct security controls into their software delivery. Security practices and testing are performed earlier in the development lifecycle…” — Wikipedia entry for DevSecOps
Slide 28
“Shifting security left” Image credit: Devopedia
Slide 29
Image credit: Threatpost
Slide 30
Progressive Delivery
Slide 31
“Progressive delivery is continuous delivery with fine-grained control over the blast radius.” — James Governor, RedMonk
Slide 32
Image credit: LaunchDarkly
Slide 33
Image credit: LaunchDarkly
Slide 34
Is it a “release”, or a “deploy(ment)?”
Slide 35
Deploy
Slide 36
Slide 37
Slide 38
Release
Slide 39
Slide 40
Image credit: Wikipedia
Slide 41
Continuous {Integration|Deployment}
Slide 42
Slide 43
Slide 44
Scrumban!
Slide 45
Slide 46
Slide 47
Quick History of CI/CD 1991
Slide 48
Quick History of CI/CD 1991 1997
Slide 49
Quick History of CI/CD 2001 1991 1997
Slide 50
Quick History of CI/CD
Slide 51
Quick History of CI/CD
Slide 52
Quick History of CI/CD
Slide 53
Software Development without CI/CD
Slide 54
Software Development without CI/CD Image source: Oursky
Slide 55
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
Slide 56
CI == Continuous Integration ● Merge code changes often Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website
Slide 57
CI == Continuous Integration ● ● Merge code changes often Run automated tests to validate builds Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website
Slide 58
CI == Continuous Integration ● ● ● Merge code changes often Run automated tests to validate builds Only integrate tested code into code base Code Shared Code Repo CI/CD Runtime Test Scan for Vulnerabilities Build Website
Slide 59
CI == Continuous Integration ● ● ● ● Merge code changes often Run automated tests to validate builds 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
Slide 60
Image credit: Product Coalition
Slide 61
CD == Continuous Deployment the practice of automatically deploying new software releases to target environments Build Website Server deployment Active Users
Slide 62
CD == Continuous Deployment ● Build Website Faster release cycles Server Deployment Active Users
Slide 63
CD == Continuous Deployment ● ● Build Website Faster release cycles Low-risk releases Server Deployment Active Users
Slide 64
CD == Continuous Deployment ● ● ● Build Website Faster release cycles Low-risk releases Higher quality Server Deployment Active Users
Slide 65
CD == Continuous Deployment ● ● ● ● Build Website Faster release cycles Low-risk releases Higher quality Lower costs Server Deployment Active Users
Slide 66
“Is CI/CD a TOOL?”
Slide 67
“It depends…” -every DevOps Advocate
Slide 68
Slide 69
Are there benefits to CI/CD?
Slide 70
CI/CD Benefits ● Commit more often = improve team productivity & efficiency ● Ship new features quickly = faster speed to market ● Faster ROI for new features = ID product/market fit ● Higher quality, more stable code = same in your products ● Access to new features faster = Increased customer satisfaction ● Keep devs happy and shipping code
Slide 71
I feel the need… the need for SPEED!
Slide 72
72
Slide 73
CI/CD Benchmarks for high performing teams Suggested Benchmarks Throughput The average number of workflow runs per day Duration The average length of time for a workflow to run Mean time to recovery The average time between failures & their next success Success rate The number of successful runs / the total number of runs over a period of time Merge on any pull request 10 minutes Under 1 hour 90% or better on default branch
Slide 74
Full Report https://circle.ci/ssd2022
Slide 75
Thank you. For feedback and swag: circle.ci/jeremy Timeline.jerdog.me IAmJerdog jerdog /in/jeremymeiss
