all day devops: devops and all the continuouses
Post on 13-Jan-2017
105 Views
Preview:
TRANSCRIPT
www.ranger4.com
DevOpstastic
Helen Beal
DevOps & All the
Continuouses
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
Continuous Funding
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
Continuous Integration
(CI)
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
Continuous Integration
Each check-in is validated by• An automated build• Automated unit,
integration and acceptance tests
Continuous integration is a development practice that requires developers to integrate code into a shared repository on a daily basis.
9Integrating regularly in production-like environments makes it
easier to quickly detect and locate conflicts and errors.
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
Continuous Delivery
(CD)
www.ranger4.com
DevOpstastic
Continuous Delivery (1)
• Extends continuous integration• Provides fast, automated
feedback on the production-readiness of systems
• Prioritizes keeping software deployable over working on new features
• Enables push-button deployments on demand
• Reduces deployment risks and enables quicker user feedback
12
Continuous delivery is a methodology that focuses on making sure software is always in a releasable state throughout its lifecycle.
Continuous delivery does not mean that you are deploying every day or every hour.
It means that you COULD release when needed.
www.ranger4.com
DevOpstastic
Continuous Delivery (2)
Commit Code
Build and Test
Acceptance Test
Deploy to Prod
and Test
Release
Automated Trigger
Manual Trigger
Stop the line when tests fail
Test StagingProd
Feedback – test results, monitoring data, etc.
.
Dev
13
Automated tests in production-like environments assure the code and environment operate as designed and are always in a deployable state
Deployment is the installation of a specified version of software to a given environment (e.g., promoting a new build into production).
www.ranger4.com
DevOpstastic
The Three Ways
www.ranger4.com
DevOpstastic
The First Way:Improve Flow
www.ranger4.com
DevOpstastic
The Three Ways
www.ranger4.com
DevOpstastic
Continuous Testing
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
Shift Left:Build Quality
In
www.ranger4.com
DevOpstastic
Continuous Deployment
(CDep?)
www.ranger4.com
DevOpstastic
Continuous Deployment (1)
• Removes the manual step in the Continuous Delivery pipeline
• Results in multiple deployments per day
21
Continuous deployment is a set of practices that enable every change that passes automated tests to be automatically deployed to production.
Continuous deployment may not be practical or possible forcompanies constrained by regulatory or other requirements.
www.ranger4.com
DevOpstastic
Continuous Deployment (2)
Commit Code
Build and Test
Acceptance Test
Deploy to Prod and
TestRelease
Automated Trigger
Manual Trigger
Stop the line when tests fail
Test StagingProd
Feedback – test results, monitoring data, etc.
Dev
22
Code deployed into production may be invisible to customers, but features can be run and tested by internal staff.
Release is the process or event of making a feature (or set of features) available to a segment of customers.
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
“Never let a known defect
pass downstream.”
www.ranger4.com
DevOpstastic
“Continuous Release Deployment”
www.ranger4.com
DevOpstastic
Continuous Measurement
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
Ideation
Integration
ValidationOperation
Realisation
DevO
ps
The DevOps Loop ©Ranger4
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
Continuous Monitoring
www.ranger4.com
DevOpstastic
The Three Ways
www.ranger4.com
DevOpstastic
The Second Way:Amplify Feedback
Loops
www.ranger4.com
DevOpstastic
The Three Ways
www.ranger4.com
DevOpstastic
Time for a
FRESH APPROACH?
35
Sonatype Nexus Lifecycle
• Precisely identify component and risks
• Remediate early in development
• Automate policy across the SDLC
• Manage risk with consolidated dashboard
• Continuously monitor applications for new risks
www.ranger4.com
DevOpstastic
Continuous Performance Management
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
Continuous Innovation
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
Continuous Experimentatio
n & Learning
www.ranger4.com
DevOpstastic
The Three Ways
www.ranger4.com
DevOpstastic
The Third Way:Experimentation
& Learning
www.ranger4.com
DevOpstastic
Continuous Job Satisfaction
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
"The world as we have created it is a process of our thinking. It cannot be changed without changing our thinking."
Albert Einstein
www.ranger4.com
DevOpstastic
Organizing around people...
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
“Holacracy structures your organisation for
evolution.”
www.ranger4.com
DevOpstastic
Continuous Teaming
www.ranger4.com
DevOpstastic
www.ranger4.com
DevOpstastic
Continuous Everything!
www.ranger4.com
DevOpstastic
The Continuous Release Cycle or ‘DEVOPS LOOP’
www.ranger4.com
DevOpstastic
Ideation
Integration
ValidationOperation
Realisation
DevO
ps
The DevOps Loop ©Ranger4
www.ranger4.com
DevOpstastic
Continuous Improvement
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
SOURCE: Ranger4’s ‘How Continuous is Your DevOps?’ Survey (Q1 2016)
www.ranger4.com
DevOpstastic
Be DevOpstastic
top related