Profile builds with Cloud Manager

[Fanindra_Surat]

Hi All,

We have different teams managing different tenants of a site, on a single AEM instance. Each team needs to do a deployment for their own tenant independently.

We have an option of going with a Maven Multi module project in a Single GIT repo, where each module corresponds to a single tenant, and we can have profile based builds to do a deployment for each tenant independently. Does ACM support profile based builds? I don't seem to find any related documentation around this.

Any suggestions / solutions please..

Thanks.

[vanegi]

Check these documents https://docs.adobe.com/content/help/en/experience-manager-cloud-manager/using/getting-started/create...

https://maven.apache.org/guides/introduction/introduction-to-profiles.html,it tells about  Maven Profiles that can be used to define how the build should be different in different environments, including Cloud Manager.

Thanks!!

[Fanindra_Surat]

This talks about managing builds on different environments using environment variables. But, I am looking for performing multiple profile builds based on the need to a single environment.

For Ex: On Single DEV environment I want to do a build of module1 (using profile1) today, and a build of module2 (using profile2) next week.

[Singaiah_Chintalapudi]

I don't think the CM supports the profiles. You can create a two different release branches for each site and checkin the changes to those respective branches individually. You can use the release branch to deploy them to AMS servers using CM.

After deployment, merge those release branches back to master so your master repo would be in sync.

Thanks,

Singaiah

[Shashi_Mulugu]

@kautuk_sahni , @kaushal_mall can you please help here

[kaushal_mall · Accepted solution]

Is this for AMS or Cloud Service?

In AEM Cloud Service, you cannot install parts of the code base, every deployment creates a new image and your complete code package has to be deployed every time. If Cloud Service is on the roadmap already, I'd try to stick to the best practices for that. Even though it might be possible for you to do this on AMS.

FWIW, this document explains what you are looking to do https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/cr... 

The ideal goal is to have automated tests, also, IMO, with multiple tenants, the sooner you catch the bugs, the better. lots of customers wait until Stage to merge all the code and deploy once, this is too late to cause issues. Deploy everything together on dev, write automated tests, catch bugs early.

[Fanindra_Surat]

This is for AMS currently, but there is a planned upgrade to Cloud Service towards the year end. So, a scalable solution helps.

Thanks in Advance.

[kaushal_mall]

In AEM Cloud Service, you cannot install parts of the code base, every deployment creates a new image and your complete code package has to be deployed everytime. If Cloud Service is on the roadmap already, I'd try to stick to the best practices for that. Even though it might be possible for you to do this on AMS.

[kaushal_mall]

FWIW, this document explains what you are looking to do https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/cr...

[Shashi_Mulugu]

@kaushal_mall will it not become heavy lift build and subsequent regression impact to validate everything's if we can only deploy large set instead of individual module. Thoughts here

[Fanindra_Surat]

@kaushal_mall Thanks for that, this very well explains why a profile or partial build is not an option for AEM Cloud Service. At the same time, as @Shashi_Mulugu mentioned isn't it a downside for large orgnaisations that host all their tenants on a single AEM instance and if they want to roll out minor updates to one of their tenant? Your thoughts here?

[kaushal_mall]

The ideal goal is to have automated tests, also, IMO, with multiple tenants, the sooner you catch the bugs, the better. lots of customers wait until Stage to merge all the code and deploy once, this is too late to cause issues. Deploy everything together on dev, write automated tests, catch bugs early.

[Shashi_Mulugu]

Thanks Kaushal this helps

[Fanindra_Surat]

Perfect. Thanks for your thoughts Kaushal.

[anuragg41105887]

@kaushal_mallgreat to hear from you, hope you are doing good. Our ask was whether we can deploy individual projects as modules from within a parent project, on demand using profiles. The link you provided clearly calls out why that's not possible in AEM as a cloud service. We actually raised this with the dedicated adobe support for one of our clients and to my surprise below is the response what we received. 

o  You can have only 1 pipeline per environment but can manage multiple builds through maven profiles

o   Maven profiles support : Pipeline variables are identical between AMS and Cloud Service (CS) so maven profile is supported in CS as well.

o   You may explore env.CM_BUILD variable for setting up profile variables. Go through below link, see section "Activating Maven Profiles in Cloud Manager"

https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/cr...

Looks like , either we are missing something or Adobe support response is not right. Your thoughts?

Stay Safe

[Yonit]

This documentation no longer appears to be available. Any chance there is an updated link?

[kaushal_mall]

Hi @anuragg41105887, I have no idea what the context of the support ticket was and an out of context response is a little hard to read. Either ways, you have your answer :-). FWIW, this is pretty clear from the docs and not sure if a support ticket is needed to begin with. I hope you and your family are doing ok.

[RajaShankar]

@Fanindra_Surat - how did you resolved this.I too have same issue with multi tenant if one wants to rollback due to various other intgeration applications rollback then its getting hectic. Please suggest