Once you have configured your Production Pipeline (repository, environment, and testing environment), you are ready to deploy your code.
Click Deploy from the Cloud Manager to start the deployment process.
The Pipeline Execution screen displays.
Click Build to start the process.
The complete build process deploys your code.
The following stages are involved in the build process:
Additionally, you can review the steps from various deployment processes by viewing logs, or reviewing results, for the testing criteria.
The Stage Deployment, involves the following steps:
The Stage Testing, involves the following steps:
The Production Deployment, involves the following steps:
The Schedule Production Deployment is enabled while configuring the pipeline.
Using this option, you can either schedule your production deployment or click Now to execute the production deployment immediately.
The scheduled date and time is specified in terms of the user’s timezone.
Click Confirm to verify your settings.
Once you confirm the deployment schedule, your code deployment completes.
The following screen displays, when Now option is selected from the above step.
The following section describes how AEM and dispatcher packages are deployed in the stage phase and in the production phase.
Cloud Manager uploads all target/*.zip files produced by the build process to a storage location. These artifacts are retrieved from this location during the deploy phases of the pipeline.
When Cloud Manager deploys to non-production topologies, the goal is to complete the deployment as quickly as possible and therefore the artifacts are deployed to all nodes simultaneously as follows:
Cloud Manager determines whether each artifact is an AEM or dispatcher package.
Cloud Manager removes all dispatchers from the Load Balancer to isolate the environment during the deployment.
Unless configured otherwise you can skip Load Balancer Changes in Dev and Stage Deployments, that is, detach and attach steps in both non-production pipelines, for dev environments, and the production pipeline, for stage environments.
This feature is expected to be primarily used by 1-1-1 customers.
Each AEM artifact is deployed to each AEM instance via Package Manager APIs, with package dependencies determining the deployment order.
To learn more about how you can use packages to install new functionality, transfer content between instances, and back up repository content, please refer to How to Work with Packages.
All AEM artifacts are deployed to both the author and the publishers. Run-modes should be leveraged when node-specific configurations are required. To learn more about how the run-modes allow you to tune your AEM instance for a specific purpose, please refer to Run Modes.
The dispatcher artifact is deployed to each dispatcher as follows:
httpddirectory. Immutable files are not overwritten. Any changes you make to immutable files in your git repository will be ignored at the time of deployment. These files are core to the AMS dispatcher framework and cannot be changed.
Cloud Manager expects the dispatcher artifact to contain the full file set. All dispatcher configuration files must be present in the git repository. Missing files or folders will result in deployment failure.
Following the successful deployment of all AEM and dispatcher packages to all nodes, the dispatchers are added back to the load balancer and the deployment is complete.
You can skip Load Balancer changes in development and stage deployments, that is, detach and attach steps in both non-production pipelines, for developer environments, and the production pipeline, for stage environments.
The process for deploying to production topologies differs slightly in order to minimize impact to AEM Site visitors.
Production deployments generally follow the same steps as above, but in a rolling manner: