DevOps Pipeline Deployment Issue
I am getting below error while running DevOps pipleline. The App is not able to move to next stage (QA). The error is below. Please let me know how to resolve this issue....
Error in deploying pipeline application MyBankAccount:01.01.01There are aged updates in the archive. Exiting the import process. List of aged updates: DATA-ADMIN-OPERATOR-ID ACCOUNTAPPROVER, DATA-ADMIN-OPERATOR-ID ACCOUNTINITIATOR,
Accepted Solution
Express Scripts
US
If the operator instances in SOR are latest than QA , you will not encounter aged updates . If SOR doesnot have latest instances, you will see aged updated during deployment and manual intervention is mandatory in that case.
Updated: 3 Dec 2018 2:39 EST
Pegasystems Inc.
IN
Which version of deployment manager is being used?
From Deployment Manager 4.x onwards there are options to override or skip aged updates.
In case of lower version of deployment manager(3.x), please resolve aged updates manually and proceed further.
Soon there is plan to release deployment manager 3.4.x where user will be given option to override or skip aged updates from Deployment Manager.
Express Scripts
US
You are seeing aged updates for the operator records as they might have been updated in your QA instance(might be manually) and you have older records in SOR system .To resolve aged updates, you need to update/resave ACCOUNTAPPROVER,ACCOUNTINITIATOR operators in your SOR system and trigger deployment again.
Evonsys
IN
Our Requirement is copying operator instances from one environment to another environment. After the deployment using devops is done, user can able to login and verify the deployed application without doing any manual updation on the environment.
Evonsys
IN
The aged issue resolution requires manual update. But the actual requirement is without manual interaction we need the deployment for operator instances and deployed user can login and check the deployment.
Accepted Solution
Express Scripts
US
If the operator instances in SOR are latest than QA , you will not encounter aged updates . If SOR doesnot have latest instances, you will see aged updated during deployment and manual intervention is mandatory in that case.