Manage deployment of multiple parallel & incremental releases
How can we manage the deployment of the same application involing parallel development for future releases?
Example: Lets say we have two releases R1 & R2 targeted to PROD in Oct-2019 & Jan-2020.
In QA, both the application versions are available and we want to avoid deploying the data instances, classes, etc of release 2 when we are deploying the R1 code using deployment manager.
There is no issue with versioned rules as application package will take care of the versioned rules. But how can we package the data instances only related to that specific release
If you already know the releases, you can create different product rule including the version of the rulesets you want to deploy and include these product rules in different pipelines.
Since you already know that data instances are tagged to rulesets and not to ruleset versions, we cannot avoid the data instances getting deployed. For the scenario you have mentioned in the example, if you have less number of data instances,Then you can create two product rules and two pipelines for the respective product rules, you can include the data instances using the pzInskey in one of the product rule.
You can use the pipeline with the product rule which is including the data instances for the release in which you want to deploy them, Otherwise use the other one.
Keep up to date on this post and subscribe to comments
- Release Dates & Support for Pega Products
- Deployment Manager Release Notes
- How can i deploy Pega AMP application (Buil on ML8 and later) using AMP management center? Where can i get the required url,user id and password information
- Data Integrity in Build & Deployment Automation