Skip to main content
close Search
Close search

Challenge

Inspecting a Deployment Manager pipeline

4 Tasks

10 mins

Visible to all users
Beginner DevOps English

Scenario

As the Release Manager for your organization, you are responsible for managing the application deployment pipelines with Deployment Manager. You have Development, Staging, and Production environments for your application life cycle and the orchestrator instance from where you manage the deployment pipeline. In this challenge, you focus on becoming familiar with the functionality of a pipeline and how it can catch issues before the pipeline goes to Production. 

Deployment Manager architecture

The following table provides the credentials you need to complete the challenge.

Role

User name

Password

Release Administrator

DMReleaseAdmin

rules123!

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Detailed Tasks

1 Inspect a pipeline in Deployment Manager

  1. Log in to Deployment Manager as the Release Administrator  with user name DMReleaseAdmin using password rules123!.

    Several pipelines are visible; each represents a different application release pipeline.
     
    Pipeline landing page
  2. Click any tile to view the pipeline, for example, the UplusCS pipeline.

    Color

    Description

    Blue

    Active pipeline with an ongoing deployment

    Red

     A deployment that has failed somewhere

    Grey

    An inactive pipeline

2 Explore features of the pipeline

In the pipeline, explore the following features.

Pipeline features Description
Pipeline model  The stages and steps of the pipeline necessary to get to production. Accessible from Actions > Pipeline model.
Deployment actions Controls the actions for a particular deployment, such as pause, abort, rollback, view logs and reports.
Application details Defines which application the pipeline will package and publish to production. Accessible from Actions > Pipeline settings > Application details.
Environment details Defines which Pega environments are associated with the different stages of the pipeline. Accessible from Actions > Pipeline settings > Deployment stages.
Pipeline reports The various KPIs (Key Performance Indicators) for the builds. Accessible by clicking Actions > View Report.
Starting Deployments Starts a deployment process as defined by the Pipeline model.
Deployment history Shows the details of the previous deployments. This feature is collapsed by default under the currently active deployment.
Browse Artifacts

Shows all the application archives that were generated during previous deployments. There are two repositories represented: Development Repository, and Production Repository. You can access these repositories by clicking Actions > Browse Artifacts. The Development Repository stores any application archive generated from the Development stage. The Production Repository stores any archive that has completed all testing and validation and is ready for deployment to production.

Manual approval (Approval for production)

This step is meant to provide some form of approval before proceeding with the pipeline. Common use cases include approval for deploying to higher environments and manual regression or acceptance testing.

Review the Pipeline Model for Uplus_CS to see where a Manual Approval step is configured.

Deployment details This feature displays the details of what has been deployed to a particular stage (or environment). You can access the deployment details by clicking on the deployment ID under each stage.
Switch to Dev Studio The Deployment Manager Operator menu includes an option to Switch to Dev Studio on the Deployment Manager instance. This feature can be useful if you need to run the Tracer tool or check log files to troubleshoot issues by using Deployment Manager (as distinct from pipeline specific issues).

3 View the pipeline model

You can view the stages and steps of the pipelines that define the deployment workflow necessary to get to Production.

  1. Click Actions > Pipeline model to access the workflow.
  2. Inspect the pipeline model for the Uplus_CS pipeline. 
    Pipeline model

4 Run a deployment

Run through the deployment in a pipeline and get familiar with how a pipeline runs in Deployment Manager and all the functionality that is available when a deployment is active. You can use the Uplus_CS to explore all the functionality related to running a deployment.

  1. In the Development tile, click Start deployment to begin deployment in the UPlus_CS pipeline.
  2. In the Start deployment dialog box, click Generate new artifact.
    Note: You can choose to give the deployment a custom name at this point.  

    As the deployment runs, it executes the tasks defined in the pipeline model that you previously explored, and the deployment tiles refresh with the task status of as it completes.

  1. Explore the errors in the pipelines and see if you can view more details of the failures caught in the pipeline.
    Note: For the purpose of this challenge, you are not looking to fix these failures caught in the pipeline. Instead, get a sense of the checks that your Deployment Manager pipeline performs and the failures that can block a deployment.
  2. When a deployment task fails in a stage, click View error to access the failure.
    Once a task fails, the task awaits user action, and the following options are displayed.

Deployment action

Description

Resume from current task

Resumes the current deployment from the current task; this is useful if you want to retry the failed task for any reason.

Skip current task and continue

Skips the current failed task and continues to execute the next task in the pipeline.

Abort

Stops the current deployment and no further tasks are executed.

View logs

Allows you to view the log output of the current deployment.

View report

Allows you to view the KPIs associated with the current deployment.

Rollback

Rolls back the current deployment in that environment. Rollback enables you to get back to a known working state of the application in the environment.  

Note: On 8.4 environments, the rollback option is scoped to the application defined in the pipeline. However, in older releases of the platform that are supported, the rollback impacts the entire environment.


If you are having problems with your training, please review the Pega Academy FAQs.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

Suggest an edit

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