Understanding split deployment pipelines in AEM
Split deployment pipelines in Adobe Experience Manager (AEM) help manage code promotion between environments. This article explains how they function, why validation on Stage is mandatory, and what to do when promoting releases to Production.
Description description
Environment
Adobe Experience Manager (AEM)
Issue/Symptoms
- The issue arises when attempting to deploy a release to Production that was previously deployed to Stage but is no longer present on Stage.
- The expectation is that previously validated releases promote directly to Production without redeployment on Stage.
Resolution resolution
- Deploy code or releases to Production only after validating them through the Stage pipeline.
- Use the same branch for both Stage and Production deployments to ensure proper validation. Avoid configuring a separate branch for production-only deployments, as this bypasses required checks on Stage.
- Before promoting a release to Production, make sure it is currently deployed and validated on Stage.
- If you need to promote a previous release, redeploy it on Stage first, then proceed with promotion to Production.
Note: AEM doesn’t maintain records of previously deployed artifacts on Stage for later promotion to Production at will. Only the latest deployment from Stage can be promoted directly.
3d58f420-19b5-47a0-a122-5c9dab55ec7f