Pipeline migration

1. Import the Deployment Manager 5.x RAPs and restart the server.
2. Log in to Deployment Manager using the DMReleaseAdmin operator.
3. In the lower-left corner of the application, click the Operator icon, and then select Switch to Dev Studio.
4. Open the operator record, and then update the default access group to SuperAdmin.
5. Log out of the application, and then log in as the DMReleaseAdmin operator.
6. On the Deployment Manager banner, click the info icon.
7. Click Migration assistant.
8. In the Pipeline Migration section, select the pipelines that you want to migrate.
   Note: Migrate dependent pipelines first. View dependencies link provides details of all pipeline dependencies.

9. Click Migrate.
10. Confirm the pipeline migration by clicking Submit.
11. When the migration is complete, the pipelines indicate the status of their migration:

    Success

    Indicates that the migration of the pipeline is successful. Expanding the row provides additional details on the pipeline migration.

    Fail

    Indicates that the creation of pipeline failed. Click View log to understand the cause of the failure.

    Not migrated

    Indicates that the pipeline is not migrated and the user can start the migration as required.

12. If pipeline migration fails due to a loading error, ensure that the open ruleset in which pipeline case types are stored is present in the Deployment Manager 5.x application stack.

Migrating the operator

After a successful update to the 5.x version, you can update operators from the Migration assistant page. Operator migration migrates the existing roles to associate them with selected operators.

1. On the Deployment Manager banner, click the info icon.
2. Click Migration assistant.
3. In the Operator Migration section, select the operators that you want to migrate.
4. Click Migrate.
5. Confirm the operator migration by clicking Submit.
6. The operators table provides the status of operator migration:

   Success

   Indicates that the selected operator migration succeeded.

   Fail

   Indicates that either role or operator migration failed. For more information, you can click View update logs on the Migration assistant page.

   Not migrated

   Indicates that the operator is not migrated and the user can start the migration as required.

   Note: Operators that you migrate manually to version 5.x are not tracked by the operator migration feature.

Updating access group

If you are updating to version 5.x, ensure the PegaDevOpsFoundation:Administrators access group is updated to point to version 5 of the PegaDevOpsFoundation application. Perform this update for all candidates that are updated to PegaDevOpsFoundation 5.x.