nCino RBC Deployment Rollback
Last updated
Last updated
Rollbacks are an indispensable pillar in the realm of systems that undergo continuous evolution. They provide a safety net, enabling you to revert to a known, stable state if something goes wrong.
This feature allows users to perform a rollback of the deployments—if rollbacks were enabled when creating the deployments.
To be able to perform rollbacks on the deployments, users must mark the deployments for rollback when configuring deployments.
Log in to your ARM account.
Go to the nCino module.
Rollbacks can either be performed through CI Jobs or Feature Deployment.
Once in the nCino module, click on the 'Create CI Job' button.
Enter the required information to configure the CI Job creation.
In the Preview and Save section, users can toggle the button to enable the rollback option.
Initially, the slider is disabled. Users must toggle the button to turn on the 'Enable rollback' option, as shown in the following picture.
On enabling the 'Enable rollback' option, users can continue to 'Save' the job.
While enabling the 'Enable rollback' option, users can click on the question mark and read the message: “Please note that the data of this rollback will be retained for a period of 30 days and will be deleted as the retention period elapses.”
Upon saving the job, users are directed to the 'Job List' page as shown.
On landing on the 'Job List' page, users can continue and run the job they created by clicking on the ‘play’ icon.
Once the build run is completed, users can see that the 'rollback' button is available on the 'job results' page.
When the build is completed successfully, users can download the snapshot of the backed-up data by hovering on the list icon beside the 'Rollback' button in the 'Job Details' page, as highlighted in the following screenshot.
Users can initiate the rollback from the 'Job Results' page directly or the 'Details' page.
Users can see the 'Rollback' button in the following screenshot on the 'Job Details' page.
Upon clicking the ‘Rollback’ button, users are prompted to decide whether to go ahead with the 'Rollback’ operation as shown in the image below.
As the 'Rollback' build is in progress, the page looks like the following:
Once the 'Rollback' is completed successfully, the 'Job Details' page looks like the following:
A new build will be added to the list of the build in the following format: 'Rollback' - < Build No >
Users can roll back the builds as often as needed.
Initiate a 'Feature Deployment' by clicking on the 'Feature Deployment' button.
Continue to input the ‘Source’ and ‘Destination’ configuration details.
On entering all the required details, click on the 'Create Dataset & Deploy' button.
On clicking the 'Create Dataset & Deploy' button, a popup with the 'Enable Rollback' option is displayed.
Select the checkbox to enable the rollback of this deployment.
Users can see an information icon beside the 'Enable Rollback' button that says, “Please note that the data of this rollback will be retained for a period of 30 days and will be deleted as the retention period elapses.”
Until the deployment is completed, it is not possible to perform a 'Rollback' on the deployment.
Click the 'Deploy' button to deploy the build.
Only upon completion of the deployment is the 'Rollback' option available.
Observe the ‘Rollback’ option, both on the 'Deployment History' page and on the 'Job Details' page.
Once the deployment is finished, users can download the backup snapshot of the deployment marked for ‘Rollback.’
Click on the 'Rollback' button to roll back the deployment.
Once the 'Rollback' is completed, then the iteration number will be updated.
While the 'Rollback' is in progress, the 'Re-Deploy' and 'Rollback' buttons are grayed out until its completion.
Observe the ‘Rollback’ iteration in the logs by expanding the deployed build, as shown below.
Rollback functionality is now supported for the Orgs selected for post-deployment activities. Please choose the selected Orgs in the highlighted section of the CI job creation flow.
What happens during the rollback of the deployments on the destination Org?
Insert: The inserted records in the destination Org are deleted.
Update: Updates to the destination Org are reverted to their original state.
