Skip to main content

Migrating application update changes to non-production environments

Suggest edit
Updated on April 12, 2022

After completing the update on non-production environments, migrate the application update changes to your non-production environments. By migrating your update fixes to your non-production environment, you ensure that your application is updated with the latest features and capabilities after an update.

Repeat the following procedure for each deployment pipeline:
  1. If the pipeline is not open, in the navigation pane of Deployment Manager, click Pipelines and then click the name of the pipeline.
  2. Expand the Deployment History pane, and then identify the deployment that was used as part of the production update. This is usually the most recent deployment.
  3. Click the View Reports link for the deployment.
  4. Click Application artifacts.
  5. In the Application artifacts dialog box, in the Production artifact section, click Copy relative path to copy the file path of the production artifact.
  6. Migrate your changes to non-production environments:
    • In the standard deployment pipeline, use ad hoc tasks to deploy the archive to each non-production environment, using the file path from step 4. For more information, see Performing ad hoc tasks.
      • If you are not using Deployment Manager, locate the application archive that updated the application in production and manually import it into each environment. For more information, see Importing rules and data by using the Import wizard.

    Did you find this content helpful? YesNo

    Have a question? Get answers now.

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

    We'd prefer it if you saw us at our best.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us