Skip to main content

Rolling back a blue/green deployment

The blue/green deployment method allows you to roll back to a previous state if anything goes wrong. You can roll back a blue/green deployment if the process fails with errors, or at any other point before your blue/green deployment is complete.

Interactive rollback checkpoints​

When performing an interactive blue/green deployment, there are explicit checkpoints where you must approve the deployment to continue. At any of these checkpoints, you can choose to abort the deployment and roll it back instead.

Database schema upgrade checkpoint​

At this stage, the green server cluster is running your target configuration, and generates a deployment report. The deployment report might indicate that your target configuration is not blue/green deployment compatible. There has been no application downtime at this point, the database has not been changed, and all production traffic is still being handled by the blue server cluster and your base configuration.

Green cluster start checkpoint​

At this stage, the database schema deployment is complete. If the database schema upgrade failed, or you find issues with the database, you can roll back the blue/green deployment. The database schema has changed, but no data has changed, and all production traffic is still being handled by the blue server cluster and your base configuration.

Rolling back at this point does not automatically restore your previous database schema. Because any blue/green allowable schema changes are backwards compatible, schema changes might not be needed. If the schema upgrade failed, determine the reason for the failure and whether it requires any schema changes to fix. Changing the database schema is a manual process that you must handle separately before attempting the next deployment.

Deployment completion checkpoint​

At this stage, the green server cluster is handling REST and SOAP API requests, the users have been notified of potential downtime, and API requests that require writing to the database are temporarily failing. Some production traffic is now being handled by the green server cluster and your target configuration. It is important to quickly make the decision to approve deployment completion or to roll back.

If you roll back at this point, the green sever cluster is stopped, and blue server cluster is restarted. Production traffic is all routed back to the blue servers, and UI and batch processes will restart with your base configuration on your blue server cluster.

Blue/green rollback procedure​

  1. In Guidewire Home, navigate to the planet containing the deployment to roll back.
  2. Under Applications and add-ons, select InsuranceSuite.
  3. Select Roll back blue/green deployment.
  4. Navigate to the application instance that is being deployed. The Current activity panel provides a link, or you can find the link in the tile for the application.
  5. Log in to the application, then press Alt+Shift+T to open the Server Tools page.
  6. In the sidebar, select Upgrade and Versions.
  7. Depending on the state of the deployment, select either Cancel or Initiate Backout.