Introduction
Sooner or later, despite our best efforts, bugs can still make it to production. When this happens, time is of the essence.
Tracking down bugs in production, implementing a fix and shipping the fix can all take time. The longer this takes, the longer bugs currently in production stay in production.
Sometimes it's not only safer but easier to rollback to an earlier release. Doing so means that your users' experience remains unaffected, while you can isolate and fix the bugs in your code at your own pace.
Table of contents
How to rollback
To rollback to an earlier release, jump into your Site Overview in the Linc interface:
Under the Active Releases section, click the orange Rollback button:
This will open a dialogue where you can view prior releases for your site:
When rolling back, it's important to make sure that the version you're rolling back to is in good working order.
You can verify the health of a prior release by clicking the Preview release button:
Clicking the Preview release button will open a preview link allowing you to preview the bundle you would like to re-release.
Once you're satisfied that you want to rollback to a given prior release, check the provided checkbox and then click the Override Release button:
This action will cause Linc to re-deploy the bundle associated with this prior release to your production release infrastructure.
Once the rollback succeeds, the Active Releases section of your Site Overview will change to indicate that a rollback has taken place:
Here we can see a red status message with the text Auto releases paused:
This message indicates that the release we just rolled back to is now pinned. This means that even if you push a commit to your release branch, nothing can be released to production until auto releases are resumed.
Resume auto releases
With auto releases paused, the Active Releases section of your Site Overview now includes a purple button with the text Resume auto releases:
Clicking this button will open a confirmation dialogue displaying the latest commit on your release branch:
Here, you verify which commit you will be rolling forward to, and certify that the bundle associated with the commit is in working order by viewing the provided preview link:
Once you're ready to roll forward, click the Resume auto releases button to return to fully automatic releases:
The dialogue will close and Linc will then automatically deploy the latest commit from your release branch:
With that, you've now returned to automatic releases!
