Artifact History and Rollback feature provides users with the ability to access previous build images for any particular application and make a rollback to the desired version.
A maximum of five previously deployed build images are available for the user to choose for rollback.
The primary use case for this feature is when the user has registered an incorrect build for any application and wants to roll back to the previous stable version, then the user can choose any previously built image from the artifact history list and perform a rollback.
- To use this feature, atleast one or more artifact (or image) needs to be registered for a particular application.
- If there is no image registered, a message will be displayed on live release page with the text No Artifact has been mapped to this application.
If no other build images exist for an application, the rollback button in live releases page will be disabled.
- Login to Facets Control Plane.
- Select the Environment in your defined Blueprint.
- Navigate to the Resources tab from the sidebar and select the application from the list for which you want to view the history.
- On the Live Release page, the Current Registered Artifact section will display the currently registered image if any.
- Click on the Rollback button to view a list of previously registered artifacts.
The rollback functionality is embedded with the artifact history screen. You can follow the same steps listed above to reach this screen.
- The artifact history page will show a list of upto five previously registered artifacts.
- To perform rollback, select the rollback icon on a previously registered image.
- A confirmation dialog box will popup to verify the rollback. Click on Confirm to proceed.
- If the rollback is successful, the dialog window closes, a success toaster is displayed and both the current image and history list are refreshed.
- If the rollback is unsuccessful, the dialog window closes and a failure toaster is displayed.
The change of registered image as selected by a user will only be enforced on the next release of the environment.
Updated 6 months ago