Multiple git repo configuration in production pipeline | Community
Skip to main content
B
bhagchand
Level 3
May 16, 2022
Solved

Multiple git repo configuration in production pipeline

  • May 16, 2022
  • 4 replies
  • 1515 views

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      

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 joerghoh

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-cloud-manager/managing-code/enterprise-team-dev-setup.html?lang=en

 

4 replies

Sanjay_Bangar
Community Advisor
Sanjay_BangarCommunity Advisor
Community Advisor
May 16, 2022

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.

    B
    bhagchandAuthor
    Level 3
    May 16, 2022

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

      MayurSatav
      Community Advisor and Adobe Champion
      MayurSatavCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      May 16, 2022

      Hi @bhagchand ,

       

      Have you checked this official documentation ?

      https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/working-with-multiple-source-git-repositories.html?lang=en

       

        Jagadeesh_Prakash
        Community Advisor
        Jagadeesh_PrakashCommunity Advisor
        Community Advisor
        May 16, 2022

        @bhagchand Why no we create parent project which have both projects

          B
          bhagchandAuthor
          Level 3
          May 16, 2022

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

            joerghoh
            Adobe Employee
            joerghohAdobe EmployeeAccepted solution
            Adobe Employee
            May 18, 2022

            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-cloud-manager/managing-code/enterprise-team-dev-setup.html?lang=en

             

              Terms & ConditionsAccessibility statement

              Loading footer...