Best Practices of using Deployment Manager for larger built on Apps

Pega-as-a-Service
, , , , ,
1

Hi,

We recently installed Deployment Manager 5.6, trying to setup CICD using it.

We’ve 5 app stacks as a built on & total 50 rulesets, when packaging as application excluding data records it is coming close to 4 GB.

I m tying to see what are the best practices,

  • Do we have to package our product rule at application or ruleset level?
  • Deployment pipeline should be at application level or it has one with listing all dependencies?
  • If there is need for parallel development for future releases, how we can achieve this?
  • Can we follow release level pipeline with product predefined & major minor listed within the product?

Please guide me, & if there is any documentation please share.

thank you.

2
  1. Pega’s recommended practice is to package using a Product rule defined for the application, not ad‑hoc per ruleset, so you preserve a consistent, deployable application snapshot.
  2. Deployment Manager is designed for application‑level pipelines: each pipeline is tied to a specific application name and version (e.g. App 01.01). Built‑on applications and other dependent apps are handled as dependencies rather than manually listed rulesets; you normally have a separate pipeline for each major deployable application and let Deployment Manager manage dependencies and ordering
  3. To support parallel releases (e.g. R1 and R2 in flight), use separate application versions and separate product rules/pipelines per release stream, all built on the same lower‑level apps
  4. you can follow a release‑level pipeline approach: one pipeline per release, with a predefined Product rule that encodes the “major.minor” version of the application and rulesets.
  5. A 4GB package is unusual, check if you whether history, old ruleset versions, and test rulesets are being included unnecessarily. And, whether data instances should be moved to separate products or initialized via data transforms/jobs instead of being in every deployment package