Deployment pipe-line is failing due to CHECKSUM issue. | AEM Community Blog Seeding

Deployment pipe-line is failing due to CHECKSUM issue. by Rules of AEM

Abstract

AEM Developers, Infrastructure Engineers regularly come across a challenge on building the AEM code & dispatcher module use to get failed while mvn build. The article addresses in a simple way on how to understand the mechanisms of dispatcher module build, and gives a detailed explanation of how it can be resolved.

This is use full for building the code for a deployment via Pipeline either it is Adobe Cloud manager or Jenkins.
This error is caused as the dispatcher owner does not not want you to change/modify few of its default files which are marked as immutable in dispatcher server.
You can find full list of immutable files on of dispatcher provided by Adobe.
https://helpx.adobe.com/experience-manager/kb/ams-dispatcher-manual/immutable-files.html


Issue :- In AEM while doing the deployment it is being seen , user get the exception , Maven mandatory check failed.

Solution :- To make sure you do not modify the default files the maven dispatcher module forces the file checksum verification method.

All these checksum values can be find in the.

<>/dispatcher/pom.xml

SAMPLE POM FILE



src/conf.d/available_vhosts/aem_author.vhost

xxxxxxxxxxxxxxxxxxxxxxx

md5

There have been changes detected in a file which is supposed to be immutable.





src/conf.d/available_vhosts/aem_publish.vhost

xxxxxxxxxxxxxxxxxxxxxxx

md5

There have been changes detected in a file which is supposed to be immutable







To get the issue resolved you have 2 options.
Option 1 - you should make sure the chcksum value present in pom.xml is same as the corresponding file. - Correct and recommended way
Option 2- You can simply comment the lines in pom.xml for the files which you do not want to be verified.

Read Full Blog

Deployment pipe-line is failing due to CHECKSUM issue.

Q&A

Please use this thread to ask the related questions.