| Table of Contents |
|---|
Refresh or Clone is process whereby Production environment is copied in to development environments. This can cause loss of code changes on environment that was refreshed. Post Refresh Request enables an environment to be brought to its original state after it has been refreshed from another environment. Post Refresh process will identify all the projects that are different between the Refreshed To and Refreshed From environments. If a project is package-based, then it will also determine which files are different between the Refreshed To and Refreshed From environments. If there are file differences then for each package-based project two packages will be created. First package which will be the Sync package that contains all the files that are currently deployed to the Refreshed From environment. The second package, Refresh package will include all the files currently deployed to the Refreshed To environment . Files that are only deployed to the Refreshed To environment will be marked as destructive in the Sync package. The following steps are performed to complete the post refresh request.
...
Request Status | Description |
|---|---|
Pending | Initial status when the process is started. |
Sync Build | Build executions of Sync packages for package-based projects. |
Refresh Build | Build executions of Refresh packages for package-based projects. |
Sync | Workflow request that runs in Refreshed To environment, sync the state of projects and files in FlexDeploy identical to the Refreshed From environment. |
DeployingSubmitted | Workflow requests that runs in Refreshed To environment, deploying all original changes to Refreshed To environment before the clone. |
CompleteCompleted | All the workflow requests for the post refresh are Completed or Rejected. Note : If any Folders has Approval or Scheduled Windows configured, Post Refresh workflow request for Sync State or Deploy will go to Pending Approval Or Scheduled status. If any of these Approval/Scheduled tasks are Rejected, Post Refresh will ignore the project for the Rejected task and continue processing the next project. |
Failed | If any build, sync workflow requests failed, or Stop On Error selected and one or more deploy request Failed or Abort requested. |
...
Post Refresh Requests
To view the Post Refresh Requests, select Topology from the menu, then select the Post Refresh tab. The results will be displayed based on user’s access to Target Groups and Environments.
...
To view a Post Refresh Request details click on the id.
...
Recover From Post Refresh Failure
Once a Post Refresh Request is initiated, the execution may fail due to various reasons. There is no option to resume a failed request. Lets go through few scenarios and understand follow steps to fix a failed request.
There are 3 different requests initiated for each request, Build, Sync and Deploy.
Build requests created only for package-based project. If any one of Build requests failed, click the Execution Id link and look for the failure reason. Fix configuration or other settings related to the error. Then again re-try the Post Refresh request for the same Target Group and Refreshed From/To environments.
Sync state failures. Sync State failures are very rare as there is no real execution for a project as it updates the FlexDeploy state related to projects and files.
For a Post Refresh request, Failed Sync State workflow requests shouldn’t cause any issues for the project, but we need to follow few steps for the successfully completed Sync State workflow requests.
...
In the above screenshot, SYNCSTATE for XXHR Data Fixes failed and XXHR and XXHR2 completed successfully.
We need to manually submit the DEPLOY request for XXHR and XXHR2 projects using the Build request for Refresh packages.
In the below screen shot, Sync_2329517 is completed for XXHR, Now go to XXHR project, submit the deploy request for package Refresh_2329517.
Similarly, for XXHR2, follow the same step and deploy the request for package Refresh_2329517.
You need to follow this steps for all the Projects(package-based) where Sync State is successful.
...
Deploy Failures. If a Deploy workflow request failed, we need to look into the plugin logs for the cause of the failure. Once the issue is fixed, we need to re-submit the deployment request.
In the below, XXHR Data Fixes workflow request 2329536 failed. Now click the execution id
...
link 2766842 and check the plugin log for error, do the fix.
Once fixed, re-submit the Deployment again for workflow request 2329536.
Follow the same for other failed deployments as well.
...