LinkedIn
Copied!

Table of Contents

Configuring additional settings in 5.3.x

Version:

Only available versions of this content are shown in the dropdown

As part of your pipeline, users can optionally receive notifications through email when events occur. For example, users can receive emails when tasks or pipeline deployments succeed or fail. For more information about the notifications that users can receive, see Understanding email notifications.

For either new Deployment Manager installations or upgrades, you must configure settings on the orchestration server so that users can receive email notifications. For more information, see Configuring email accounts for new Deployment Manager installations.

Additionally, you can configure Jenkins if you are using Jenkins tasks in a pipeline. For more information, see Configuring Jenkins in 5.3.x.

  • Configuring email accounts on the orchestration server

    Deployment Manager leverages the Default email account from 5.x version and the DMEmailListener email listener. If you are configuring email accounts for the first time, specify your details for this account in Pega Platform. For more information, see .

  • Configuring Jenkins in 5.3.x

    If you are using a Run Jenkins step task in your pipeline, configure Jenkins so that it can communicate with the orchestration server.

  • Configuring Deployment Manager notifications

    You can enable notifications to receive updates about the events that occur in your pipeline. For example, you can choose to receive emails about whether unit tests failed or succeeded. You can receive notifications in the Deployment Manager notifications gadget, through email, or both. By default, all notifications are enabled for users who are configured in Deployment Manager.

  • Dynamic system settings

    Deployment Manager exposes a few Dynamic System Settings (DSS) to override the default behavior. See below for a list of configurations available to override the default behavior. All of these settings are optional and are not required by default. Carefully evaluate each configuration before configuring for your application.

  • Creating and using custom repository types for Deployment Manager

    In Deployment Manager 3.1.x and later, you can create custom repository types to store and move your artifacts. For example, you can create a Nexus repository and use it similarly to how you would use a Pega Platform-supported repository type such as file system. By creating custom repository types, you can extend the functionality of Deployment Manager through the use of a wider variety of repository types with your artifacts.

  • Managing test cases separately in Deployment Manager

    Using Deployment Manager, you can package and deploy test cases separately on the candidate systems in the pipeline. When you configure a pipeline in Deployment Manager, you specify the details of the test package that you want to deploy. To define on or until which stage the test artifact can be deployed, you can set the configuration using the Deploy task. Check Deploy test artifact? on the Deploy task of the stage where test artifact shall be deployed.

  • Configuring SSO and LDAP

    Deployment Manager supports LDAP and Single Sign-On (SSO) authentication, and assigns user roles based on the configuration settings in the active directory and SSO.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.