Table of Contents

Pipeline modeling

Frequently asked questions about pipeline modeling in Deployment Manager.

How can I support more than four stages in a pipeline?

If you are on v5.x of Deployment Manager, you can configure more than four stages in a pipeline, and name the stages according to your organization terminology. Additionally, you can leverage the environment templates that prescribe the required tasks for a stage.

Why can I only have one deployment per stage?

You can have multiple, different, pipelines deploying to the same environments, however the challenge with parallel imports on the same environments still persists. If the same set of rules are being imported, there could be failures that are hard to diagnose and fix.

There are two primary reasons for supporting only one deployment per environment at the same time:

  • Pega import process is not thread safe, so if same rule is modified during parallel deployments (application imports), deployments could fail, and it will be very challenging to identify which deployment was the source of the failure.
  • Before each deployment, a restore point will be created on that environment. So, in case of parallel deployments, if we are not sure which deployment have caused the failure it again will be challenging to identify which deployment restore point to use.

Can I have a pipeline progress to a stage only after manual approval?

Yes. Deployment Manager supports manual tasks. Add the task to an appropriate stage and assign it to the stakeholder who should approve it. Deployment will not proceed until the task is approved.

The operator record for the stakeholder needs to exist on the Deployment Manager environment. If the email address is set correctly on the operator record, the approver will get an email notification as shown. Ensure the operator is associated with a role to approve a task.

Can I alter the default workflow of a pipeline?

Deployment Manager offers a simple and standardized workflow to automate deployments to production. We strongly recommend you not to alter or edit any of the out of box rules shipped with Deployment Manager. Any such change may break existing functionality and it will make it significantly more difficult to upgrade to newer versions in the future.

If you want to add a custom task, the custom task infrastructure allows you to create tasks specific to your DevOps needs. See Creating and using custom tasks for more information.

How can I use the deploy existing artifact functionality in Deployment Manager 5?

Deploy existing artifact feature is not available in Deployment Manager 5. Deployment Manager now has ability to configure more than four stages. By utilizing the multispeed functionality, you can achieve various speed at different phases of the pipeline and control the versions that are promoted to higher environments. See Using multispeed deployments for more information.

Can I use OAuth authentication type for communication between orchestrator and candidate?

Deployment manager currently uses OAuth for communication between candidate to orchestrator but communication from orchestrator to candidate is performed using basic authentication. We are planning to support this in future releases.

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.