Profile builds with Cloud Manager | Community
Skip to main content
Fanindra_Surat
Community Advisor
Fanindra_SuratCommunity Advisor
Community Advisor
August 27, 2020
Solved

Profile builds with Cloud Manager

  • August 27, 2020
  • 5 replies
  • 5666 views

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.

 

    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 kaushalmall

    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/creating-aem-application-project.html#environment-variables 

    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.

    5 replies

    vanegi
    Adobe Employee
    vanegiAdobe Employee
    Adobe Employee
    August 27, 2020

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

    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
      Community Advisor
      Fanindra_SuratCommunity AdvisorAuthor
      Community Advisor
      August 27, 2020

      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
        Singaiah_Chintalapudi
        August 27, 2020

        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
          Community Advisor
          Shashi_MuluguCommunity Advisor
          Community Advisor
          August 27, 2020

          @kautuk_sahni , @kaushalmall can you please help here

            K
            Adobe Employee
            kaushalmallAdobe EmployeeAccepted solution
            Adobe Employee
            August 27, 2020

            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/creating-aem-application-project.html#environment-variables 

            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.

              K
              Adobe Employee
              kaushalmallAdobe Employee
              Adobe Employee
              August 27, 2020
              FWIW, this document explains what you are looking to do https://docs.adobe.com/content/help/en/experience-manager-cloud-service/onboarding/getting-access/creating-aem-application-project.html#environment-variables
                RajaShankar
                Community Advisor
                RajaShankarCommunity Advisor
                Community Advisor
                November 30, 2020
                @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
                  Terms & ConditionsAccessibility statement

                  Loading footer...