We have requirements to migrate multiple sites under the same parent brand with their individual AEM Code Repositories to AEW as Cloud Service.
So, we wanted to understand the best solution, to migrate these multiple projects to AEMaaCS.
We also have one project having all common codes for these multiple sites.
Also, we wanted to understand the solution should be compatible with Adobe Cloud GIT Repository.
Creating Multiple Programs or Single Program with Multi Sub-Modules Project
@arunpatidar @Jörg_Hoh @lukasz-m @Lokesh_Vajrala @Saravanan_Dharmaraj @kautuk_sahni
Solved! Go to Solution.
Views
Replies
Total Likes
You can use a Single Program with Multiple code repositories, where you will have a Single Stage and Production environment with a production pipeline and multiple dev environments with non-production pipelines.
You mentioned you have a common/shared repository and multiple brand repositories - with multiple repositories, I would recommend looking at Git Submodule approach or Using Multiple Repositories as Arun suggested. You can have multiple repos in Cloud Manager repo, but you want to have a single repo in the cloud manager that is configured with production pipeline for deployments.
As you mentioned, you already have a code in common repository then you can use the single repository.
It is also possible to use multiple repositories with cloud manager, https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/managing-code/multi...
Make sure you follow also
You can use a Single Program with Multiple code repositories, where you will have a Single Stage and Production environment with a production pipeline and multiple dev environments with non-production pipelines.
You mentioned you have a common/shared repository and multiple brand repositories - with multiple repositories, I would recommend looking at Git Submodule approach or Using Multiple Repositories as Arun suggested. You can have multiple repos in Cloud Manager repo, but you want to have a single repo in the cloud manager that is configured with production pipeline for deployments.
Views
Likes
Replies