Embracing On-Prem delivery with DevOps
summary
Company packages one shared codebase into six docker containers and pushes them to customers via replicated admin console with preflight checks, air‑gap bundles and channel promotion so a vetted internal build becomes a customer-visible release with one click. CI builds nightly, runs ~600 functional regression tests plus performance checks, and versioned pipeline definitions let teams recreate and hotfix 12–24‑month‑old releases. Result: on‑prem delivery becomes routine rather than a six‑month waterfall.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:00STORY TIME
- 2:33THE DOWNSIDE
- 6:53REASONS YOU MAY NOT BE ABLE TO AVOID ON-PREM
- 9:20CONSIDERATIONS
- 16:54CUSTOMER SIDE
- 17:49VENDOR SIDE
- 18:10CHANNELS
- 19:02ONE-CLICK UPGRADE
- 20:28ON-PREM CONTAINER ORCHESTRATION
- 23:38CONTINUOUS DELIVERY OF ON-PREM
- 24:17TODAY ON-PREM IS ROUTINE
related talks
05mDelivery-Transformation DevOps-Pipeline
30mDevOps and Agility Immersed in the Production Factory
01h 01mA team's transition to Continuous Delivery
30mModern Continuous Delivery
22mProgressive Delivery: The Logical Evolution CI/CD
19mDevOps Challenges: The Key Is Technical Excellence
01h 03mYet Another Continuous Delivery Talk
16mRevolutionizing DevEx: Accelerating Software Development
