Pipeline deployment fails after pipeline version upgrade in AEM Cloud Manager
In Adobe Experience Manager (AEM) Cloud Manager, deployment pipelines fail repeatedly or remain in a running state after a pipeline version upgrade. The issue occurs even when the same code previously deployed successfully and no recent Dispatcher changes were made. To fix this issue, review and update pipeline and Dispatcher configurations to align with the upgraded pipeline version.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Manager (all versions)
Symptoms
- Deployment pipelines fail repeatedly after a pipeline version upgrade.
- Pipeline execution remains in a running state for an extended period (for example, more than one hour).
- The same code base built successfully before the upgrade.
- No recent changes were made to the Dispatcher configuration.
- Builds succeed on local instances but fail in Cloud Manager after the upgrade.
Cause
Configuration changes or incompatibilities introduced during the pipeline version upgrade affect the deployment process or the way Dispatcher configurations are handled.
Resolution resolution
To fix this issue, follow these steps:
- Navigate to the pipeline execution page in Cloud Manager.
- Cancel any currently running pipeline that is stuck or failing.
- Review the Dispatcher vhost files and related configuration to confirm that no unintended changes were made.
- If possible, compare the current configuration with the last known working version.
- If the issue appears to be related to the web tier, update the pipeline configuration to temporarily ignore the web tier and retry the deployment.
- Re-run the pipeline after making the necessary configuration adjustments.
- Verify that the pipeline completes successfully.
- Optionally, validate that the same configuration builds successfully on a local instance to rule out local configuration issues.
recommendation-more-help
experience-cloud-kcs-help-kbarticles