Learn how to use Cloud Manager to create and configure non-production pipelines to deploy your code. If you would first like a more conceptual overview of how pipelines work in Cloud Manager, please see the document CI/CD Pipelines.
Using the Pipelines tile in Cloud Manager, the Deployment Manager can create two different types of pipelines.
This document focuses on non-production pipelines. For details on how to configure production pipelines see the document Configuring Production Pipelines.
There are two types of non-production pipelines:
Once you have set up your program and have at least one environment using the Cloud Manager UI, you are ready to add a non-production pipeline by following these steps.
Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization and program.
Access the Pipelines card from the Cloud Manager home screen. Click on Add and select Add Non-Production Pipeline.
On the Configuration tab of the Add Non-Production Pipeline dialog, select the type of pipeline you want to create, either a Code Quality Pipeline or a Deployment Pipeline.
Provide a description for your pipeline in the Non-Production Pipeline Name field.
If you chose to add a Deployment Pipeline, select the target deployment environment from the Eligible Deployment Environments dropdown.
Provide the repository where the pipeline should retrieve the code.
Define your deployment options.
Under Deployment Trigger, define what event activates the pipeline.
For deployment pipelines, under Important Metric Failures Behavior, define the behavior of the pipeline when an important failure is encountered in any of the quality gates.
Dispatcher Configuration - The Deployment Manager role can configure a set of content paths which will either be invalidated or flushed from the AEM Dispatcher cache when a pipeline is run. These cache actions will be performed as part of the deployment pipeline step, just after any content packages are deployed. These settings use standard AEM Dispatcher behavior. To configure:
Under PATH provide a content path.
Under TYPE, select the action to be taken on that path.
Click Add Path to add your specified path. You can add up to 100 paths per environment.
Click Save to save your pipeline.
Once you have configured the pipeline, you need to deploy your code. Please see the document Code Deployment for more details.
This video provides an overview of the pipeline creation process, which is detailed in this document.