| 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.
...
| Info |
|---|
Sync State is a new workflow type used for Post Refresh. When it is executed for a Target Group and an Environment (Refreshed To), the workflow will make FlexDeploy deployment state files and projects identical to the clone(Refreshed From) environment. |
...
View History of Post Refresh Requests
To view the previously executed (or current) 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.
...
Initiate Post Refresh Request
To initiate a new Post Refresh Request, select the values for the following fields
...
Click the Sync & Re-Deploy to initiate the post refresh request process to sync and re-deploy the projects. When the Request Status is Complete, the refresh is done.
...
Once the process is initiated, you will be taken to the Post Refresh Request details page to see the status and progress.
...
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. |
Submitted | Workflow requests that runs in Refreshed To environment, deploying all original changes to Refreshed To environment before the clone. |
Completed | 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.
...
Recovering 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.
...