Running the Migrated Repository Through a Pipeline for Installation in AEM CS is a process that involves migrating an Adobe Experience Manager (AEM) project from an older version (e.g., AEM 6.5) to AEM as a Cloud Service. AEM as a Cloud Service is a cloud-based version of AEM that provides enhanced scalability, flexibility, and automatic updates. Builds are done through Pipelines that are orchestrated by Adobe’s Cloud Manager Web UI.
The repository and codebase also have a different structure and architecture than previous AEM versions. If we are working with an older repository, such as one compatible with AEM 6.5, it must first be migrated to the structure needed by AEMaaCS.
The process begins with using the AEM repository migration tool. This conversion generates a target folder containing the project source and Maven sub-projects. Once the repository is migrated, it can be run through the Cloud Manager Pipelines to streamline its build and installation into AEMaaCS’s cloud environments.
Introduction:
Here we explain the process of running a migrated repository through a pipeline for installation in AEM as a Cloud Service (AEM CS). We will start with a project built for AEM 6.5 and use the AEM repository migration tool to convert it into a structure compatible with AEM CS. Then, we will go through six steps to get the converted project up and running in AEM CS.
Step 1: Creating a New Repository in Cloud Manager
To begin, we need to create a new repository in Cloud Manager where our migrated project will reside. This repository is crucial as it allows the pipelines to install projects into AEM CS.
Step 2: Copying the Migrated Project and Initializing as a Git Repository
Next, we will move the migrated project into its own local folder outside the existing 6.5 project. We will initialize this folder as a new Git repository and push it to the Cloud Manager repository we created in the previous step.
Step 3: Configuring the Pipeline
In this step, we will configure a pipeline in Cloud Manager to use the repository we just created. We will select the appropriate type of pipeline based on our needs, and then specify the repository as the source code for the pipeline.
Step 4: Running the Pipeline and Handling Errors
Once the pipeline is configured, we can run it to deploy our project in AEM CS. If there are any errors during the build process, we will need to troubleshoot and fix them before proceeding.
Step 5: Addressing Package Skips
In this step, we will address a common issue related to package skips in AEM CS builds. We will ensure that at least one package, typically the “all” package, is not skipped during the build process. We may need to modify the parent POM file to remove the “cloudManagerTarget” entry.
Step 6: Pushing Changes and Completing the Pipeline
Finally, we will push the necessary changes, including the modified POM file, to the Cloud Manager repository. Once the changes are pushed, we can resume the pipeline and monitor its progress. If everything goes well, our converted repository will be successfully installed in AEM CS.
Conclusion:
To effectively run a migrated repository through a pipeline for installation in AEM CS, follow these steps. This process ensures seamless compatibility with AEM as a Cloud Service and allows us to leverage the benefits of a cloud-native deployment system. By implementing proper configuration and thorough error handling, we can streamline the transition from an older AEM version to AEM CS. Rest assured, the Atypical Design team is always ready to provide assistance throughout the migration process.