Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

What are the best things that we can implement to reduce AEMaaCS CICD build execution time

Avatar

Level 3

Build takes to much time to verify the code changes, It will go through the multiple steps like mentioned below 

  • Build & Unit Testing
  • Code Scanning
  • Build Images
  • Product Functional Testing
  • Custom Functional Testing
  • Custom UI Testing

Is there any way to reduce some steps or build will focus on the changes only rather than considering entire code repository for each build

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hello @Nilesh_Mali  - 

 

Though, we do have option to run the pipeline in Emergency Mode (AMS instances) thereby skipping the security and performance test steps.

 

However, there is no option to skip code quality test while working with AEM as Cloud Service. Refer https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

 

Yet, to reduce some deployment time you can consider creating Apache/Dispatcher “web tier” configuration thereby allowing  Apache/Dispatcher configurations to be deployed separately as their own pipeline – decoupled from deployment of the rest of the codebase.

Refer & Read : 

https://www.opsinventor.com/speeding-up-aem-cloud-service-deployment-the-dispatcher-only-pipeline/ 

 

 

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Hello @Nilesh_Mali  - 

 

Though, we do have option to run the pipeline in Emergency Mode (AMS instances) thereby skipping the security and performance test steps.

 

However, there is no option to skip code quality test while working with AEM as Cloud Service. Refer https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

 

Yet, to reduce some deployment time you can consider creating Apache/Dispatcher “web tier” configuration thereby allowing  Apache/Dispatcher configurations to be deployed separately as their own pipeline – decoupled from deployment of the rest of the codebase.

Refer & Read : 

https://www.opsinventor.com/speeding-up-aem-cloud-service-deployment-the-dispatcher-only-pipeline/