Concept to Code to Runtime - Simplify, Enable, Exploit
summary
Jenkins fails every three days until branching is fixed, and a branching tweak cuts change-related issues by 30% while improving code convergence by 60%. A DevOps platform runs 300 pipelines across 19 countries with 2,500 developers, 30% of team time spent on support, and a chatbot that logs ~20 queries/day. Built items include a UFW starter framework, a Rasa-based chatbot, CI/CD for AS400 (RPG), and a software delivery lake on ELK that maps user stories to commit-level code quality and delay drivers.
AI-written summary · about
chapters (8)
- 0:00Concept to Code to Runtime Intro
- 1:09Srivatsan TA: What I Do
- 8:42What if I Say
- 12:36Let's take one Application Profile
- 14:56Anchor DevOps Differently: From Enabler to Influencer
- 18:24Let us take an example: Application Architecture and Design
- 21:29Concept to Code to Run
- 23:36What can DevOps provide across the stages
related talks
29mFrom scheduled builds to commit triggered pipelines
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain
27mAutomation, Innovation and Continuous Delivery
46mThe Software Factory
23mShipping Quality Software in Hostile Environments- 27mAutomation, Innovation and Continuous Delivery
42mAutomation, Innovation and Continuous Delivery
44mFrom Zero to Federated at the Speed of Jenkins