Building Continuous Integration and Feedback
summary
KeyBank moves a 20-hour test cycle down to a 12-minute test suite by parallelizing unit, API, functional (Selenium/WebDriver), security (Sonatype/Black Duck) and small performance (JMeter/DynaTrace) checks into CI pipelines. Builds run on Jenkins with Kubernetes agents and artifacts go to Nexus; logs and metrics stream via Kafka into an Elastic stack for visualization. Real events: 500,000 users hit a new UI at 30 logins/sec and the team ships 10 production releases in four days. Some releases still contain 158 days of manual steps.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:42Path to Financial Wellness
- 1:06KeyBank DevOps Journey
- 4:08Customer Day 1
- 5:40Evolution of the team
- 7:15Taking a step back
- 8:55Cloud Native Team
- 10:02Continuous Integration and Delivery
- 12:13Digital Intelligence
- 13:37Automated Delivery Pipeline
- 14:58Data ingestion
- 15:34Testing
- 17:02Automated Gates
- 18:41Scaling
- 19:45C ISO
- 20:35Legacy Code
- 22:32Kubernetes
- 25:06SelfService
- 26:43Metrics
- 28:15Release and Versioning
- 30:43Architectural Pattern
related talks
35mMassively Continuous Integration: From 3 days to 30 minutes
28mKeeping Developers Happy with a Fast CI
34mUsing Test Automation for Continuous Integration, Delivery and Quality
53mTransforming testing methodologies: From manual to robust strategies
31mWeb Integration Testing Under the Microscope
31m#testedAF: Test All the Things (Not Just Your Units)
33mBanking on Innovation & DevOps
47mFrom bi-annual to fortnightly releases in 4 months for 15 teams and one monolith