Packaging a release on your development environment
As part of the Standard Release process for migrating your application changes from development to production, you set up and package the release on your shared development environment.
This Standard Release process applies to both on-premises and Pega Cloud Services environments. As a Pega Cloud Services customer, if you use this self-service process to release changes to your application, you are responsible for those changes. For more information, see Change management in Pega Cloud Services and Service level agreement for Pega Cloud Services.
This process involves completing the following steps:
- Creating the release target (ruleset version)
- Locking the release
- Creating the application archives
After you set up and package the release, you are ready to deploy the changes to your staging or production environment.
- Creating the release target
When developers merge changes by using the Merge Wizard, they must select the ruleset version to which to merge them. The release engineer is responsible for ensuring that each release has an unlocked ruleset version that acts as the release target and into which these merges can be performed. Developers are responsible for merging their branches into the correct, unlocked ruleset version and addressing any conflicts.
- Locking the release
After all merges are completed, the release engineer locks the applications and rulesets to be released. They are also responsible for creating the new, higher-level ruleset versions and higher-level application rules for the next release.
- Creating the application archives
For each release, you create one or two RAP archives, depending on the changes you made to your application. The user who exports the archives must have the zipMoveExport privilege.
Previous topic Rolling back a problematic deployment Next topic Creating the release target