AEM cloud Migration - Is MAJOR categories issue must have to fix?

[sameryadav]

Hi,

we are doing AEM as cloud migration, and in BPS report there Critical and Major categories issue.

So here question is for all Major categories issue is it must have to fix or it will work if not fixing the Major categories issue?

Thanks

[arunpatidar · Accepted solution]

Hi @sameryadav 

You must fix Critical type of issue to avoid pipeline failure.

For each of these gates, there is a three-tiered structure for issues identified by the gate.

• Critical - Issues that cause an immediate failure of the pipeline.
• Important - Issues that cause the pipeline to enter a paused state. A deployment manager, project manager, or business owner can either override the issues. If they do, the pipeline proceeds as intended. Alternatively, they can accept the issues, causing the pipeline to stop with a failure. Override of important failures are subject to a timeout.
• Info - Issues that are provided purely for informational purposes and have no impact on pipeline execution.

You will find more info at https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/using/code-quali... 

[sameyadav]

Hi @arunpatidar 

Thanks for quick response.

The URL you shared is for code quality report, The categories of issue that I am referring is Best Practice Analyzer (BPA) report.

When we ran the Best practice Analyzer report then we got some issue as MAJOR categories like:

Error: A legacy foundation custom component was found at /apps/project/components/content/itineraryTextSearch. It is deprecated and should be modernized.

Here if this type of issue we will not fix then still the build will work on AEM cloud env but what is the Risk if we are going with these type of MAJOR issue on cloud? are there any chance in future it will not work because it is already deprecated?

Thanks

[arunpatidar]

Hi @sameyadav 

It is possible that legacy code might be restricted and you can see for deprecations in upcoming releases but it is still Adobe's decision, better to check with Adobe.