Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Multiple git repo configuration in production pipeline

Avatar

Level 3

Hi Team,

Hope you are doing great.

Currently we are working on AEM as CS and one website is configured in production pipeline.

So now we want to develop one more website with different domain with one different git repo.

So can you please suggest a way to configure the same.

Thank in advance, Have a nice day      

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Why do you want to use a different git repository when you develop a 2nd presence? In my opinion it is not necessary to split that, but instead you should rather make this dependent from other criteria, e.g:

 

* the 2nd presence is developed by other developers, and they should not have write access to the code of the 1st presence; therefor you have for them a 2nd git repo.

* You share code between multiple AEM projects/customers, and therefor it's easier to push a remote repository to git repositories associated to the multiple AEM projects in Cloud Service.

 

But you need to be aware, that even if you have multiple git repositories, they will always be deployed all within the same deployment.

 

 

The documentation for it: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

 

View solution in original post

6 Replies

Avatar

Community Advisor

Hi @bhagchand ,

you can do that follow the below steps:

1.Clone your branch

2.Checkout master or dev

3.Create your new branch(diffrent website) from master give the  proper name

4. If you want the same structure then leave it as it is  or if you don't want the same structure then delete whole project and add your custom project code

5.push your branch

6.go to the adobe cloud service select deployment in that you need to select your new branch means your new environment will be pointing to your branch.

Avatar

Level 3

Okay, but in this each times we need to select branch for different sites during deployment.

Avatar

Level 3

@Jagadeesh_Prakash, this is our new requirement, Can you please share to create parent project from existing project 
Thanks 

Avatar

Correct answer by
Employee Advisor

Why do you want to use a different git repository when you develop a 2nd presence? In my opinion it is not necessary to split that, but instead you should rather make this dependent from other criteria, e.g:

 

* the 2nd presence is developed by other developers, and they should not have write access to the code of the 1st presence; therefor you have for them a 2nd git repo.

* You share code between multiple AEM projects/customers, and therefor it's easier to push a remote repository to git repositories associated to the multiple AEM projects in Cloud Service.

 

But you need to be aware, that even if you have multiple git repositories, they will always be deployed all within the same deployment.

 

 

The documentation for it: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...