Need clarifications on CI/CD Deployment Manager 4.3.2 using in Pega 8.1
We are working on implementing the CI CD deployment manager 4.3.2 in Pega 8.1 and using JFROG for the repository.
The configuration for the orchestration(master server) and candidate systems (DEV,SIT, Staging) is completed successfully and deployment process works fine.
I have following questions to continue further in exploring the CICD capability.
We have added the task Perform Manual Step to include the Approval process for each deployment. However the OOTB Deploy task is in first step and can't change the sequence. Due to which by the time flow reaches to the newly added task 'Perform Manual Step' product file is getting deployed in all the candidate systems even if we reject the task. Can we change the task sequence so that the Approval step will execute first and then the Deploy task ?
As the Orchestration system is in Pega 8.1 with Deployment Manager 4.3.2, can we use the same server for the deployment process for the applications(candidate systems) which are in Pega 7.2 and 7.3 ?
Once the deployment is success we couldn't see any provision to rollback or restore the Product which is deployed. Is this capability is not supported ?
1) As of now, for implicit tasks like "Deploy", there is no provision to move them. But , you can use a manual task in "Quality Assurance" stage to stop the deployment in further stages.
LG: I have added the additional task step for Running Test Suite , but product it getting deployed before reaching to this step irrespective of whether the Test Suite executes successfully or fails. Even if the test suite fails this product is getting deployed.
2) We recommend to have all the candidate systems to be on same pdf version and it is better to have the latest version to use all the features.
LG: I agree with the recommendation but can you please confirm if product supports it ? The reason to know this is we have 99% of apps which are in PRPC 7.2/ 7.3 and we can't ask the customer to upgrade to use the DevOps future. So before we go ahead and explore on this trying to understand if product will support this approach or not.