Add a production pipeline configuring-production-pipelines

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization and program.

Navigate to the Pipelines card from the Program Overview page.

Click +Add, then select Add Production Pipeline.

The Add Production Pipeline dialog box opens to the Configuration tab where a number of options for your pipeline must be defined. These options are grouped into collapsible sections and are described in the following steps.

1. Provide a descriptive name for your pipeline in the Pipeline Name field.

2. Under the Environments section, you define what triggers a deployment and how it should be rolled out per environment.

   1. In the STAGE section, you can define how the pipeline rolls out to your staging environment.

      • Deployment Trigger - You have the following options to define the deployment triggers to start the pipeline.

        • Manual - Start the pipeline manually using the Cloud Manager UI.
        • On Git Changes - Start the CI/CD pipeline whenever commits are added to the configured Git branch. With this option, you can still start the pipeline manually as required.

      • Important Metric Failures Behavior - During pipeline setup or edit, the Deployment Manager has the option of defining the behavior of the pipeline when an important failure is encountered in any of the quality gates. The available options are:

        • Ask every time - The default setting and requires manual intervention on any important failure.
        • Fail Immediately - The pipeline is canceled whenever an important failure occurs. It is emulating a user manually rejecting each failure.
        • Continue Immediately - The pipeline proceeds automatically whenever an important failure occurs. It is emulating a user manually approving each failure.

      

      • Deployment Options - You can accelerate certain deployment tasks.

        • Approve after Stage Deployment - This approval occurs after deployment to the staging environment before any testing is done. Otherwise, approval occurs before the production deployment, which is done after all testing is complete.

        • Skip Load Balancer changes - Load balancer changes are not made.

      

      • Dispatcher Configuration - The Deployment Manager role can configure a set of content paths that are either invalidated or flushed from the AEM Dispatcher cache when a pipeline is run. These cache actions are performed as part of the deployment pipeline step, just after any content packages are deployed. These settings use standard AEM Dispatcher behavior. To configure, do the following:

        1. Under PATH provide a content path.

        2. Under TYPE, select the action to be taken on that path.

           • Flush - Perform a cache deletion.
           • Invalidate - Perform a cache invalidation, similar to when content is activated from an authoring instance to a publishing instance.

        3. Click Add Path to add your specified path. You can add up to 100 paths per environment.

      

      note tip
      TIP
      In general, the use of the invalidate action is preferable, but there may be cases where flushing is required, especially when using AEM HTML Client Libraries.

   2. In the PRODUCTION section, you can define how the pipeline rolls out to your production environment.

      • Deployment Options - You can define the parameters controlling the production deployment.

        • Use Go Live Approval - A user with the Business Owner, Project Manager, or Deployment Manager role by way of the Cloud Manager UI must manually approve a deployment.

        • Scheduled - Halts the pipeline before production deployment to allow it to be scheduled. If this option is selected, the pipeline halts after deployment to the staging environment and prompt the user for the action to take.

          • Now - Deploys to production immediately, effectively completing the pipeline.
          • Date - Lets the user schedule a time when the deployment should be completed.
          • Stop Execution - Aborts deployment to production.

        note tip
        TIP
        See Code Deployment to learn how to set the deployment schedule or execute the pipeline immediately.

        • Use CSE Oversight - If this option is select, a CSE (Customer Success Engineer) is engaged to start the actual deployment. When creating or editing a pipeline when this option is enabled, the Deployment Manager role has the following options.

          • Any CSE - Allows any available CSE to start the deployment.
          • My CSE - Allows only the specific CSE assigned to the customer to start the deployment. This option also applies for the designated backup of the CSE if the assigned CSE is unavailable.

        

      • Dispatcher Configuration - Define the Dispatcher configuration for your production environment. The options are the same as the options for the staging environment.

Click Continue to advance to the Source Code tab where you select the type of code to deploy and configure the source repository.

1. Under Select code to deploy, choose the deployment type:

   • Full Stack Code - Code for your complete AEM application.
   • Web Tier Config - Dispatcher properties to store, process and deliver web pages to the client.

   See CI/CD Pipelines for more information about these deployment types. The remaining steps to complete the pipeline configuration depend on the type you selected. Follow the links above to jump to the relevant section of this document.

Click Continue to advance to the Stage Testing tab where you can configure AEM Sites and AEM Assets Performance Testing, depending on which products you have licensed.

1. In the Sites Content Delivery/Distributed Load Weight section, you configure site Performance Testing based on the weighting of page requests among three page sets. You can enable or disable the page sets as needed.

   • Popular Live Pages
   • Other Live Pages
   • New Pages

   

2. Under the Assets Performance Testing Distribution section, you define the test distribution of images and PDFs and define your own test assets.

   • Images - Adjust the slider to adjust the test split between images and PDFs.

   • PDFs - Adjust the slider to adjust the test split between images and PDFs.

   • Define your own custom assets by uploading them.

     1. FORMAT - Choose whether your custom asset is a PDF of an image.
     2. FILENAME - Use the file browser button to select an image from your local machine.
     3. Add Test File - Click to upload your selected asset.

   

Click Save to complete adding your production pipeline.

On the Source Code tab, define the following options.

• Repository - Defines which Git repo the pipeline should retrieve the code.

• Git Branch - Defines from which branch the pipeline should retrieve the code.
• Ignore Web Tier Configuration - When checked, the pipeline does not deploy your web tier configuration. If a web tier config pipeline already exists for the same environment, this check box is automatically selected and disabled because the web tier configuration is managed by that pipeline instead. When no web tier config pipeline exists, you can select or clear this option to control whether the full stack pipeline deploys the Dispatcher configuration.

Click Continue to advance to the Stage Testing tab. See Stage Testing for details.

On the Source Code tab, define the following options.

• Repository - From the drop-down list, select the Git repository that contains the web tier configuration.
• Git Branch - Select the branch in the chosen repository that Cloud Manager uses for the deployment.
• Code Location - Enter the path in the selected repository that contains the web tier configuration to deploy. The default location is the repository root (/).

Click Continue to advance to the Stage Testing tab. See Stage Testing for details.