Deep dive into AEM as a Cloud Service continuous delivery model
summary
Based on the Adobe whitepaper the pipeline runs module-level validations, a PR assessment that executes ~2,200 tests per PR across ~50 parallel VMs for ~25 PRs/day, then deploys to Kubernetes via Cloud Manager for 114 end-to-end tests and a customer update assessment that clones 124 customers (~250 environments) using a visual comparison tool and error-log diffs to score risk. A release orchestrator performs multi-stage canary rollouts, publishes the SDK, and achieves over 99% successful customer upgrades.
AI-written summary · about
chapters (11)
- 0:00Introduction and overview
- 1:46Always current model explained
- 3:34CI/CD pipeline structure
- 6:04Module level validation
- 6:26Pull request assessment
- 8:35End-to-end validation
- 11:23Customer risk assessment
- 15:19Release validation and SDK
- 16:24Rollout with release orchestrator
- 19:57Pipeline performance metrics
- 20:17Q&A session
related talks
02mAEM Shorts: Leveraging Cloud Manager to Optimize the DevOps Process
25mThe Cloud Native Journey at Adobe
43mLearn workflows and tips for faster deployments with RDE
35mIntelligent Deployments at Scale: Effortless Continuous Deploy...
06m⚡ Lightning Talk: Improving Release Reliability with Argo Rollouts Across 10k Customer Services
54mAdobe Experience Manager Rock Star: The Headless Challenge
37m7 Ways to Break AEM
54mFrom Code to Customer