Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Packaging a release on your development environment

Updated on April 5, 2022

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:

  1. Creating the release target (ruleset version)
  2. Locking the release
  3. 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.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us