Rolling back
Automatic rollback of a failed deployment, undoing a plan that has run, and undoing changes before deploying.
A deployment fails: nothing to do
Section titled “A deployment fails: nothing to do”If a check fails during a deployment, Fransys undoes the changes on its own: your last version stays online. The console shows Deployment failed: rolled back, your last version stays online. Fix the problem, then deploy again.
Undo a plan that has run
Section titled “Undo a plan that has run”On the page of a plan that has run, Undo this plan prepares a new, opposite plan:
- the window lists What will be undone and What can’t be undone (a deleted service, for example);
- settings go back to the value they had before that plan, even if they’ve been changed since;
- nothing runs right away: you review the undo plan, then run it like any other.
Changes you make in the console are recorded in plans too: you can undo them the same way.
Undo before deploying
Section titled “Undo before deploying”As long as changes aren’t deployed, Undo changes puts each setting back to its previous value. Nothing is deployed. See Deploy and monitor.
Go back to a version of your code
Section titled “Go back to a version of your code”With a Git repository, the safest way is to go back in the repository (a git revert, then a push): the CI builds and deploys the fixed version.
Going back to a previous version of a project in one click, from the deployment history, isn’t available yet.
Getting data back
Section titled “Getting data back”A database’s data doesn’t come back with a rollback. To start again from a backup, see Backups and restore.