Can using prpcServiceUtils to import a full rap cause inconsistency in rulesets or data
I am implmenting DevOps with Pega, my team members have followed the tech notes for Jenkins deployment and have successfully setup and have a working deployment of incremental rap files from the developers for some months now.
The developer have experience in Pega versions before 7.2.1, they are currently not providing full rulesets only incremental ruleset because they are concerned of inconsistency after using prpcServiceUtils to import a full wrap . Is it possible for prpcServiceUtils to import the latest package from Dev to tet with Pega 7.2.1 and create an issues with inconsistency of rulesets or will the objects just be overridden with the deployment?
I am implmenting DevOps with Pega, my team members have followed the tech notes for Jenkins deployment and have successfully setup and have a working deployment of incremental rap files from the developers for some months now.
The developer have experience in Pega versions before 7.2.1, they are currently not providing full rulesets only incremental ruleset because they are concerned of inconsistency after using prpcServiceUtils to import a full wrap . Is it possible for prpcServiceUtils to import the latest package from Dev to tet with Pega 7.2.1 and create an issues with inconsistency of rulesets or will the objects just be overridden with the deployment?
prpcServiceUtils.sh import
import.archive.path=fulldeploy.zip
import.mode=import
import.existingInstances=override
import.nofailonerror=false
import.compileLibraries=true
import.allowImportWithMissingDependencies=false
import.async=false
import.tracdata=false
***Updated by moderator: Lochan to update Categories; add group tag SR Exists***
Pegasystems Inc.
US
Accenture
AU
Yes the same settings are being used to import. If these should be altered based on the type of import happy to receive guidance.
The developers are worried about:
- They are worried about older rules overwriting newer ones
- Yes concern of rules being skipped or older rules being referenced
- missing components from the archive (I have explained that this is why we test and we can repackage and deploy to our test environment to verify the packaging)
I assume that during the packaging process the developers should package everything (except items that have failed unit test which would be excluded).
Then a standard import will sync the records where a version of the record not matching pxSaveDateTime already exists.
If there is a hotfix it would only load the latest pxSaveDateTime versions.
Does this mean that a standard import will load everything (To use if I want to create a new Dev) and a Hotfix import should be used for just loading the latest records and ignore the older versions? Therefore the developer concerns should not be an issue...
What do you mean by inconsistencies? Are you worried about rules being skipped from the full RAP or prior versions being overwritten by earlier ones? Here is some direction provided by Pega SME.
"Import mode will load anything that has a different pxSaveDateTime than what is in the database. Hotfix mode will only load more recent pxSaveDateTime."
More clarity is needed to understand further. Are your settings the same for partial (with exception of archive)?