Roll back an app
When a deploy goes wrong, a rollback puts the app back on an earlier image in the time it takes to start new pods, with no rebuild. A rollback is a deploy of the older image, so it uses the same rolling update and health checks as any other deploy.
A rollback does not revert your repository. It also leaves the database schema as it is, unless you restore bound databases.
Roll back an app
Section titled “Roll back an app”- Open the app.
- Go to Activity.
- In History, find the release.
- Select Roll back. To return to the previous release, select Roll back on the Live release at the top of the page.
- (Optional) Select Also restore bound databases to before this deploy. Each database returns to its checkpoint from before the deploy.
- Select Promote.
To roll back to the previous release:
orchard deploy rollback <id> --waitTo roll back to a specific release, get its ID from orchard deploy releases <id>, then run the following command:
orchard deploy rollback <id> <history-id> --waitTo restore bound databases too, add --restore-databases.
Recover from a bad deploy
Section titled “Recover from a bad deploy”- Roll back to the last working image.
- Fix the problem in the repository.
- Push the fix. If auto-deploy is on, Orchard builds and deploys it.
Restart an app
Section titled “Restart an app”A restart creates new pods on the same image. Use it for a stuck process, such as a blocked connection pool. If the image has the problem, use a rollback instead.
Open the app and select Restart in the header.
orchard deploy restart <id>Related resources
Section titled “Related resources”- Builds - Find out why a build failed before you push a fix.
- Back up and restore a database - Restore a database on its own, outside a rollback.
orchard deployreference - Every flag of theorchard deploycommands.