What are the best things that we can implement to reduce AEMaaCS CICD build execution time | Community
Skip to main content
Nilesh_Mali
Level 3
July 12, 2023
Solved

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

  • July 12, 2023
  • 1 reply
  • 577 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Tanika02

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/ 

 

 

1 reply

Tanika02
Tanika02Accepted solution
Level 7
July 12, 2023

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/