Roll back a deploy

​

Before you start

• An app with at least one earlier deploy that went live. A deploy that failed cannot be a rollback target.

​

Roll back to the previous deploy

​

Roll back to an older deploy

1

Open Deploys

Open the app and go to Deploys. Each row shows the deploy number, its state, the commit, what started it, how long it took and when.

2

Pick the deploy

Find the deploy you want. Deploys that were live and then replaced show the state Replaced. Click Log on a row to check what it built.

3

Roll back

Click Roll back on that row.

​

What happens

• The rollback runs as a new deploy with the trigger rollback. It goes live the same way as any deploy: once the app answers its health check, or its port opens when it has none. Until then the current deploy keeps serving.
• Only the code goes back. Environment variables, scaling and other settings stay as they are now.
• On an app from GitHub, the next push to the branch deploys that commit as usual. Fix or revert the change in Git before you push again.
• To go back to the newer code, roll back to that deploy the same way.

​

Do it from your tools

# Find the deploy: newest first, with id, deployment_number, status and commit
curl "https://api.rafftechnologies.com/api/v1/apps/services/$APP_ID/deployments" \
  -H "X-API-Key: $RAFF_API_KEY"

# Roll back to it
curl -X POST "https://api.rafftechnologies.com/api/v1/apps/services/$APP_ID/rollback" \
  -H "X-API-Key: $RAFF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"target_deployment_id": "DEPLOYMENT_ID"}'

raff apps deployments $APP_ID
raff apps rollback $APP_ID --target DEPLOYMENT_ID

​

Next steps