“AIOps combines big data and machine learning to automate IT operations processes, including event correlation, anomaly detection, and causality determination.” — Gartner
Slide 12
“an industry category for machine learning analytics technology that enhances IT operations analytics” — Wikipedia entry for AIOps
Slide 13
Slide 14
Image credit: Gartner Blog Network
Slide 15
Image credit: Capgemini
Slide 16
GitOps
Slide 17
Slide 18
Slide 19
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 20
Image credit: VMWare
Slide 21
DevSecOps
Slide 22
“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 23
“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 24
“Shifting security left”
Image credit: Devopedia
Slide 25
Image credit: Threatpost
Slide 26
Progressive Delivery
Slide 27
“Progressive delivery is continuous delivery with fine-grained control over the blast radius.” — James Governor, RedMonk
Slide 28
Image credit: LaunchDarkly
Slide 29
Image credit: LaunchDarkly
Slide 30
Is it a “release”, or a “deploy(ment)?”
Slide 31
Deploy
Slide 32
Slide 33
Slide 34
Release
Slide 35
Slide 36
Image credit: Wikipedia
Slide 37
Continuous {Integration|Deployment}
Slide 38
Slide 39
Slide 40
Scrumban!
Slide 41
Slide 42
Slide 43
Quick History of CI/CD
1991
Slide 44
Quick History of CI/CD
1991
1997
Slide 45
Quick History of CI/CD
2001
1991
1997
Slide 46
Quick History of CI/CD
Slide 47
Quick History of CI/CD
Slide 48
Quick History of CI/CD
Slide 49
Software Development without CI/CD
Slide 50
Software Development without CI/CD
Image source: Oursky
Slide 51
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 52
CI == Continuous Integration ●
Merge code changes often
Code
Shared Code Repo
CI/CD Runtime
Test
Scan for Vulnerabilities
Build Website
Slide 53
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 54
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 55
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 56
Image credit: Product Coalition
Slide 57
CD == Continuous Deployment the practice of automatically deploying new software releases to target environments
Build Website
Server deployment
Active Users
Slide 58
CD == Continuous Deployment ●
Build Website
Faster release cycles
Server Deployment
Active Users
Slide 59
CD == Continuous Deployment ● ●
Build Website
Faster release cycles Low-risk releases
Server Deployment
Active Users
Slide 60
CD == Continuous Deployment ● ● ●
Build Website
Faster release cycles Low-risk releases Higher quality
Server Deployment
Active Users
Slide 61
CD == Continuous Deployment ● ● ● ●
Build Website
Faster release cycles Low-risk releases Higher quality Lower costs
Server Deployment
Active Users
Slide 62
“Is CI/CD a TOOL?”
Slide 63
“It depends…” -every DevOps Advocate
Slide 64
Slide 65
Are there benefits to CI/CD?
Slide 66
CI/CD Benefits ● ● ● ● ● ●
Improve team productivity & efficiency Accelerate speed to market Identify product/market fit & ROI Release higher quality, more stable products Increase customer satisfaction Keep devs happy and shipping code
Slide 67
I feel the need… the need for SPEED!
Slide 68
68
Slide 69
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 70
Full Report
https://circle.ci/ssd2022
Slide 71
Thank you. For feedback and swag: circle.ci/jeremy
Timeline.jerdog.me IAmJerdog jerdog /in/jeremymeiss