If issues or exceptions occur in a new version of an application during the application update or after the application is updated, you can roll back the application. After the issues are fixed, update the application again. This topic describes how to roll back an application in the Enterprise Distributed Application Service (EDAS) console.

Background information

During an application update process, the application may fail to be updated due to exceptions, such as an unavailable deployment package or a health check failure. In this case, the application update process is automatically terminated and the application is rolled back.

If issues or exceptions occur in the new version of an application, you can manually roll back the application. A manual rollback can be performed in the following scenarios:
  • Rollback during the update: You can terminate the application update process and roll back the application.
  • Rollback after the update: You can roll back the application by deploying a historical version of the application.

Rollback during the update

In this example, an application is rolled back during the process of a manual phased release. If you need to release an application in phases, you can preferentially implement a manual phased release. The phased release in manual mode is more controllable. After the application is released in a phase, you can verify whether the new version of the application is valid and determine whether to continue to release the application in the next phase.
  • If the new version of the application meets expectations after the verification, you can manually continue to release the application in the next phase.
  • If an exception occurs in the new version of the application after the verification, you can roll back the application. After the issue is fixed, release the application again.
  1. Implement a phased release on an application.
  2. In the left-side navigation pane, click Change List.
  3. On the Change List page, find the change record that you want to view and click View in the Actions column.
  4. In the upper-right corner, click Rollback.
    Phased release - Process
  5. In the Confirmation message, click OK.
    After you confirm that the application is manually rolled back, the application update process is automatically terminated and the application is rolled back to the previous version. If the value of Execution Status is Succeeded, the application is rolled back. Roll back an application - Process

Rollback after the update

In this example, an application is rolled back by deploying a historical version of the application after the phased release is implemented on the application.

  1. On the Application Overview page, choose Deploy > Deploy Historical Version.
  2. In the Deploy Historical Version dialog box, select the version that you want to deploy and click Deploy This Version.
    Select a historical version
  3. In the left-side navigation pane, click Change List.
  4. On the Change List page, find the change record for the preceding operation and click View in the Actions column.
    After you select the historical version to deploy, the system starts to roll back the application to the historical version. If the value of Execution Status is Succeeded, the historical version of the application is deployed. Successful deployment of the historical version