DOES14 - Simon Storm - Promontory
summary
Promontory implements a full pipeline with push-button deployments, blue/green releases and infrastructure as code, hooks Jenkins/Puppet/Nexus/Stash/Git into Active Directory for auditable permissions, and uses Sonar and Cucumber for static analysis and test logging. A one-app rollout drops static-analysis issues from 17,000 to 4,000 issues, achieves ~80% automated test coverage but keeps a UAT spreadsheet because auditors demand proof that tests themselves are valid, and adds a custom Git hook to require AD accounts for commits.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:24Credits
- 2:38Where to Start
- 4:35Taking a Step Back... Let's Start with the Bible
- 6:48Common Sense & Agile Education
- 9:26Continuous Delivery Education
- 12:44#11 Automated Testing - Unexpected Result
- 13:15Demonstrating Maturity
- 13:29Go Digital
- 14:13Automating Sign-Offs
- 14:43Automating Documentation
- 15:08Logging Pipeline Activity
- 16:47Add one more meeting
- 17:53Orchestrate for Improved Quality
- 20:16When All Else Fails - Email!
- 20:39Source Code Control is KEY
- 20:57Demonstrate Permissions
- 21:44Code Reviews with Pull Requests
- 24:00Be Aware of Outstanding Audit Risks Get Ahead of Permission Questions
- 27:30Questions?
related talks
39mOur journey to automated releases
01h 12mPitfalls of Continuous Deployment
51mTaking AppSec to 11: Pipelines, DevOps and making things better
40mThe Butler Did It: Putting Jenkins To Work For You
01h 03mMoving Fast - without crashing
12mContinuous Deployment in a heavily regulated environment
32mFiring up a holistic Continuous Delivery Pipeline
01h 00mDeep Dive: Self-driving Pipelines: Building the Unbreakable Continuous...