Release Engineering For A Polyglot Team
summary
Polyglot builds (Java, Ruby, Node) produce immutable images and assets and Jenkins acts as a composable release platform while a homegrown UI triggers jobs and calendar schedules via APIs. Gate checks include API-queryable sanity and regression results plus traffic-only test accounts. Blue/green rollouts use blue/green via exception metrics and Istio signals to detect anomalies, and a single observability portal centralizes logs, traces and metrics. Goals track Dora targets like one day lead time and MTTR under one hour. Jenkins-based orchestration and calendar-triggered releases are in production.
AI-written summary · about
chapters (11)
- 0:00Introduction to polyglot release engineering
- 1:23DORA metrics and release impact
- 3:11Challenges in polyglot environments
- 4:36Build solutions for multiple languages
- 6:01Testing across polyglot services
- 8:27Deployment strategies and automation
- 11:36Notifications and stakeholder updates
- 13:22Jenkins as a unified platform
- 15:10Orchestration and tooling options
- 16:56Observability for polyglot systems
- 18:42Scaling release engineering function
related talks
31mRelease Engineering as a Service - The Art of Integrating with K8s
06mIgnite - Blue Green Deployments Using Terraform + Packer + Jenkins
46mThe Software Factory
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
12mContinuous Deployment in a heavily regulated environment
43mDevOps for Mere Mortals
35mJenkins Scaling and Organization for an Efficient CI
57mA continuous fairytale