Skip to main content

Deployment Manager pipeline elements

 A pipeline in Deployment Manager consists of the following elements:

  • The scope of deployment is application details.
  • The target environments in which the deployment and validation of a product or solution (an application) take place.
  • The process that outlines the tasks to perform at each target environment.

On creating a pipeline from a template, the pipeline derives the pipeline model from the selected pipeline template.

In the following image, click the + icons to learn about how different elements in a pipeline act together to form an application delivery process.

The scope of deployment for an application

A pipeline is defined for an application and a specific application version. A new pipeline requires application details that are necessary to execute the selected process.

The application details in a pipeline require the following categories of information. Each category is applicable to all or a set of pipeline templates.

  • Application packaging environment
  • Application details
  • Test application details
  • Merge policy
  • Dependencies

Application packaging environment

The application packaging environment is the system of record (SOR) or a development candidate environment that is used as the single source for an application. The configuration requires a Pega Platform™ URL and an authentication profile to establish communication between the Deployment Manager orchestrator system and the system with a specified URL.

Application details

Application details provide all the relevant application identifiers that are used by the pipeline to perform tasks on the development candidate environment.

Pipeline creation requires the following application details:

  • Application and Version: Because a pipeline is defined for an application, the application and the version are specified to identify the application that is managed by the pipeline.
  • Product rule and Version: The product rule is only required when a pipeline is configured to generate an artifact. Pega Platform supports deployments across environments by using the product rule. The product rule is an instance of the Rule-Admin-Product class.
  • Access group: Specifies the access group that is required to run tasks in an environment.

Environment and repositories

A stage in a pipeline defines a phase in the release process. Each stage serves a unique purpose and adds value incrementally to qualify a ready-to-deploy application. A pipeline template defines a pipeline model or process to solve a specific use case, and each of the stages defined in the pipeline model is associated with an environment.

An application change has to go through a defined path before the application is available to the end users.

The following are required details to define the release path:

  • Stage name is the name of the stage defined by the pipeline template.
  • Environment template is a template that predefines the recommended tasks for a stage.
  • Environment URL is the candidate environment’s URL that is used by the Deployment Manager orchestrator during deployment. 
  • Authentication profile is used to authenticate the orchestrator to establish successful communication with the candidate environment.

Artifact repository

A pipeline requires a development repository that is used to create and migrate artifacts that are evaluated as ready-to-deploy. You must specify a production repository that is used to promote an application artifact when it is ready to deploy in production.

Deployment Manager pipeline model

A pipeline model outlines the process that is defined for releasing an application to the end users. A pipeline template offers a predefined pipeline process to solve a business need.

On creating a pipeline, the user can either leverage the out-of-the-box pipeline model that is generated by the selected pipeline template or further enhance the proposed model. A pipeline model screen allows users to add, edit, or remove stages. Users can also add, edit, or remove tasks at each stage of the pipeline.

The pipeline template recommends standard stages with a predefined environment template.

Check your knowledge with the following interaction.

New pipeline

Users can create a pipeline in Deployment Manager by selecting a pipeline template. A pipeline template offers a tailored solution for a business problem.

You can create a new pipeline on the Application pipelines screen or the landing page after login.

Note:  A new pipeline creation is controlled by managePipeline privilege in Deployment Manager.
If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice