Juc deck 16x9_dev_ops_mvp
-
Upload
curtis-yanko -
Category
Technology
-
view
82 -
download
0
Transcript of Juc deck 16x9_dev_ops_mvp
Footer
#jenkinsconf
The Vision
4
Software Factory
Col
labo
ratio
n
Tra
nspa
renc
y
Qua
lity
< MTTD/MTTR, < Rework, > Quality, > Productivity/Innovation
Tools
People &
Process
Footer
#jenkinsconf
5
Culture
Culture is shared norms (behavior) and language.
If we change the behaviors and language then a new culture will emerge
The software factory is the foundation for new behaviors and an opportunity to introduce Lean language into our conversations
Footer
#jenkinsconf
State Of DevOps Report 2014 - Findings
I think they got it wrong!
Continuous Delivery is a superset in my opinion. It should read ‘Deployment Automation’
Version Control & Deployment Automation is where we start.
Footer
#jenkinsconf
10
The Art of the Possible
• All builds are release candidates• Zero-Touch Deploys for all environments• Code, Config & Data!• Jenkins for ARA at first• Create a view of what’s where• Start small
Footer
#jenkinsconf
Talk about ‘Versions’ not LATEST
Dev QA SIT UAT STG Prod
2.3
2.1
2.2
2.1
2.0
2.1
2.1
2.0
2.0
2.0
2.0
2.0
1.1
1.0
1.0
1.0
1.0
1.0
Footer
#jenkinsconf
12
Deployment Automation
• Forces discussions across silo’s• Middleware, Sys Admins, Prod Support, DBA’s• Makes the end-to-end process visible• Acceptance Test
Footer
#jenkinsconf
13
My Experience - YMMV
• <50% Deployment time• <80% in First Time Failures• <MTTD in Dev or QA• <MTTR from hours to minutes• ~40% waste removed
Footer
#jenkinsconf
14
People
• Deploy Night from 8hrs to < 2hrs• People felt engaged• No longer overwhelmed• Had the time to fix/improve processes• Once folks get a button there is no going back
Footer
#jenkinsconf
15
Going Forward
• Solve for more middleware• Tackling automated testing is doable now• Continuous Delivery seems within reach