AEM Cloud Manager: full stack pipeline fails at ‘Deploy to Dev’ due to malformed DocView XML in content package
This article addresses consistent failures in the Adobe Experience Manager Cloud Full Stack Pipeline during the ‘Deploy to Dev’ stage caused by malformed DocView XML in a content package.
Description description
Environment
Adobe Experience Manager (AEM) as a Cloud Service (all versions)
Issue/Symptoms
The Cloud Full Stack Pipeline fails consistently during the Deploy to Dev stage. Multiple pipeline executions exhibit the same behavior, with the deployment process either failing or becoming stuck for extended periods (e.g., over 1.5 hours) without progressing. No actionable error information is visible in the deployment logs.
- The issue is reproducible by triggering the full stack pipeline for the affected environment.
- No specific error messages are shown in the logs; the pipeline appears to hang or fail silently at the deployment step.
Resolution resolution
-
Identify the problematic content package
- Review the content packages included in the pipeline, focusing on recently added or modified packages.
- Check for packages generated by automated tools that may introduce malformed XML.
-
Validate DocView XML files
- Extract the content package and locate all
.content.xmlfiles. - Use an XML validation tool such as
xmllintto check each.content.xmlfile for well-formedness.
code language-none find . -name '*.content.xml' -exec xmllint --noout {} \;- Address any XML syntax errors reported by the validator.
- Extract the content package and locate all
-
Update the build process to prevent future issues
- Ensure the
ui.contentmodule is built using the FileVault Package Maven Plugin. - Run
mvn clean verifyto validate package structure and XML correctness before committing or deploying. - Reference: AEM Project Content Package Structure
- Ensure the
-
Add XML validation to the CI pipeline
- Integrate an XML validation step in the CI process to automatically check all
.content.xmlfiles for well-formedness before deployment.
- Integrate an XML validation step in the CI process to automatically check all
-
Re-run the pipeline
- After correcting any malformed XML and updating the build process, re-trigger the pipeline to verify successful deployment.
Cause
The pipeline failures were caused by a malformed DocView XML file in a mutable content package. This issue only surfaced when the problematic package was processed during the deployment step, not due to changes in Adobe’s analyzer or plugin tooling.