Best way to maintain codebase in AEMaaCS

[Ezhilcloud]

In AEM managed service we maintain a code in enterprise git and use Bitbucket for reviewing the code. How do we do the same in AEMaaCS?  As far as I know the codebase has to be in adobe git in case of AEMaaCS. Is that 100% true ?

1. Can we have an option to maintain a code in outside Adobe Git? If yes how can we create a Adobe Pipeline for code deployment ?
2. I think Adobe git does not come with web based UI meaning that we can not see code in browser. It supports command line interface, in that case how do we need code review process?

[anish-s · Accepted solution]

Hi @Ezhilcloud , Cloud manager deployment can be done only through enterprise git. However you can integrate your external managed git or bitbucket to AEMasCS GIT by following simple steps. Also you can integrate Jenkins with AEMasCS. Please refer to below links:

https://www.opsinventor.com/regarding-integrating-aem-cloud-manager-and-jenkins-diagrams-how-tos/

https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/managing-code/setup-c...

Answers to your 2 points:

1. Can we have an option to maintain a code in outside Adobe Git? If yes how can we create a Adobe Pipeline for code deployment ? - Yes, You can maintain separate git space other than AEMasCS and do all review and PR merge there. Once you are ready you can sync up this branch with AEMasCS git branch. Follow this Adobe tutorial - https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/managing-code/setup-c...
2. I think Adobe git does not come with web based UI meaning that we can not see code in browser. It supports command line interface, in that case how do we need code review process? You are correct. Adobe git doesn't come with web based UI. All code review should be done on the customer managed GIT then final release branch should be merged with Adobe GIT. - Follow the same link