Hello,
I hope you can help me on this topic.
Is there a possibility to deploy on the same environment, different repositories but not all at the same time?
Example:
Suppose we have 2 different repositories (repo A and repo B), totally independent of each other.
Both must be present simultaneously in the same environment
Each repository will have a reference pipeline in which we will deploy the reference code.
What’s the matter?
If I start the pipeline of repository A that contains only repository A,
how can I prevent the build from going to delete everything already present of repository B on the environment?
The goal is to deploy only repositories that have undergone changes, not all repositories but still keep them all on the same environment.
Is there a way to implement this?
Thanks,
Roberta
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @30991930w169,
I don't think this is possible, what you can try is to:
Good luck,
Daniel
Hi @30991930w169,
I don't think this is possible, what you can try is to:
Good luck,
Daniel
In AEM as a Cloud Service, having multiple repositories deployed individually is not feasible. This is because the cloud platform converts everything into a single immutable image as part of the deployment process.
However, you can achieve modularity and manage multiple codebases by utilizing Git submodules -https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/managing-code/gi... . With Git submodules, you can include multiple repositories as part of a single main repository. During the build process, all the submodules are combined, ensuring everything is packaged into the final image seamlessly.
This approach allows you to maintain separate repositories for different features or modules while adhering to the single-build deployment requirement in AEM Cloud.
@30991930w169 That is not possible with AEM as cloud service. But you could combine the code in the two repos into a single repo with individual repo code as submodules and then deploy.
Adding an additional point to what others have mentioned:
In AEM Cloud Manager, you cannot create more than one production pipeline per program. This limitation means you can deploy only one repository to production at a time.
To address this, consider using a merged repository or Git submodules. This setup allows you to deploy all required codebases together consistently using a single pipeline.
Short Answer: We can only deploy one code repository.
Why?
This approach, while seemingly restrictive, is actually a fundamental part of AEM Cloud's architecture.
Solution: Merge the 2 repositories as modules under a parent maven project for deployment. https://www.comwrap.com/en/blog/multi-tenancy-with-adobe-cloud-manager
Views
Likes
Replies