�۶���Ƶ

Deploy your code deploy-your-code

Learn how to deploy your code to Production using Cloud Manager pipelines in AEM as a Cloud Service.

Deploying code seamlessly to Stage and then through to Production is done through a Production pipeline. The Production pipeline execution is broken into the two following logical phases:

Only the Full Stack Code pipeline type supports code scanning, function testing, UI testing, and experience audit.

Deployment process deployment-process

All Cloud Service deployments follow a rolling process to ensure zero downtime. See How Rolling Deployments Work to learn more.

Deploy your code with Cloud Manager in AEM as a Cloud Service deploying-code-with-cloud-manager

Once you have configured your production Pipeline including repository, environment, and testing environment, you are ready to deploy your code.

The build process deploys your code through the following three ordered phases:

Stage deployment phase stage-deployment

The Stage Deployment phase involves the following steps:

Stage testing phase stage-testing

The Stage testing phase involves the following steps:

Production deployment phase production-deployment

The process for deploying to production topologies differs slightly to minimize the impact on visitors to an AEM site.

Production deployments generally follow the same steps as previously described, but in a rolling manner. These steps include the following:

This process continues until the deployment has reached all publishers and Dispatchers in the topology.

Timeouts during a deployment timeouts

The following steps time out if they are left waiting for user feedback during a deployment:

Re-execute a production deployment reexecute-deployment

In rare cases, production deployment steps may fail for transient reasons. In such cases, re-execution of the production deployment step is supported so long as the production deployment step has been completed, regardless of the type of completion (for example, canceled or unsuccessful). Re-execution creates a new execution using the same pipeline consisting of the following three steps:

In such circumstances where a re-execution is possible, the production pipeline status page provides the Re-execute option next to the usual Download build log option.

Limitations limitations

Re-execute API reexecute-API

In addition to being available in the UI, you can use to trigger re-executions and identify executions that were triggered as re-executions.

Trigger a re-execution reexecute-deployment-api

To trigger a re-execution, make a PUT request to the HAL Link https://ns.adobe.com/adobecloud/rel/pipeline/reExecute on the production deploy step state.

This link is only available for the production deploy step.

 {
  "_links": {
    "https://ns.adobe.com/adobecloud/rel/pipeline/logs": {
      "href": "/api/program/4/pipeline/1/execution/953671/phase/1575676/step/2983530/logs",
      "templated": false
    },
    "https://ns.adobe.com/adobecloud/rel/pipeline/reExecute": {
      "href": "/api/program/4/pipeline/1/execution?stepId=2983530",
      "templated": false
    },
    "https://ns.adobe.com/adobecloud/rel/pipeline/metrics": {
      "href": "/api/program/4/pipeline/1/execution/953671/phase/1575676/step/2983530/metrics",
      "templated": false
    },
    "self": {
      "href": "/api/program/4/pipeline/1/execution/953671/phase/1575676/step/2983530",
      "templated": false
    }
  },
  "id": "6187842",
  "stepId": "2983530",
  "phaseId": "1575676",
  "action": "deploy",
  "environment": "weretail-global-b75-prod",
  "environmentType": "prod",
  "environmentId": "59254",
  "startedAt": "2022-01-20T14:47:41.247+0000",
  "finishedAt": "2022-01-20T15:06:19.885+0000",
  "updatedAt": "2022-01-20T15:06:20.803+0000",
  "details": {
  },
  "status": "FINISHED"

The syntax of the HAL link’s href value is only an example. The actual value should always be read from the HAL link and not generated.

Submitting a PUT request to this endpoint results in a 201 response if successful, and the response body is the representation of the new execution. This workflow is similar to starting a regular execution through the API.

Identify a re-execute execution identify-reexecution

The system identifies re-executions by setting the trigger field to the value RE_EXECUTE.