Juc deck 16x9_dev_ops_mvp
This document discusses using Jenkins to establish a software factory approach to DevOps. It advocates creating a culture of collaboration, transparency and quality through continuous delivery practices like deployment automation. The vision is to make all builds release candidates and enable zero-touch deployments across environments to reduce waste and improve productivity. Initial steps involve using Jenkins for release automation and creating visibility into code, configurations and data across environments. Automating deployments is seen as key to driving cross-team discussions and continuous improvement. The experience of the author was that such practices reduced deployment times by over 50% and mean time to repair from hours to minutes.
Juc deck 16x9_dev_ops_mvp
- 2. Making Strides Toward Enterprise Scale DevOps with Jenkins in you Software Factory 2
- 3. …or A DevOps Minimum Viable Product 3
- 4. Footer #jenkinsconf The Vision 4 Software Factory Collaboration Transparency Quality < MTTD/MTTR, < Rework, > Quality, > Productivity/Innovation Tools People & Process
- 5. Footer #jenkinsconf 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 5
- 6. Footer #jenkinsconf Level Set 6 https://www.flickr.com/photos/minhtran/15860870273/
- 7. 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.
- 8. Footer #jenkinsconf Problem Domain and Scope 8
- 10. Footer #jenkinsconf 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 10
- 11. 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
- 12. Footer #jenkinsconf Deployment Automation • Forces discussions across silo’s • Middleware, Sys Admins, Prod Support, DBA’s • Makes the end-to-end process visible • Acceptance Test 12
- 13. Footer #jenkinsconf My Experience - YMMV • <50% Deployment time • <80% in First Time Failures • <MTTD in Dev or QA • <MTTR from hours to minutes • ~40% waste removed 13
- 14. Footer #jenkinsconf 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 14
- 15. Footer #jenkinsconf Going Forward • Solve for more middleware • Tackling automated testing is doable now • Continuous Delivery seems within reach 15