Deployment History & Rollback
Every Git deployment is recorded with its status, trigger source, commit SHA, and logs. You can review past deployments and roll back to a previous commit directly from the dashboard.
Viewing Deployment History
- Open your app's detail page and go to the Deployments tab.
- Deployments are listed in reverse chronological order (newest first).
Each deployment entry shows:
- Status indicator — Color-coded badge showing
completed,failed,deploying, orqueued. - Trigger badge — How the deploy was initiated:
- Manual — Triggered via the Deploy Now button.
- Auto — Triggered by a GitHub webhook (push to branch).
- Rollback — Triggered by rolling back to a previous deployment.
- Commit SHA — The first 7 characters of the Git commit. Clicking the SHA opens the commit on GitHub in a new tab.
- Timestamp — When the deployment started.
Real-Time Logs
When a deployment is in progress (deploying status), logs update in real time. Open the Deployments tab while a deploy is running to watch the output as each step completes.
Rolling Back to a Previous Deployment
You can roll back to any previous successful deployment that has a recorded commit SHA.
- In the Deployments tab, find the deployment you want to roll back to.
- Click the Rollback button next to it. This button only appears on deployments with a
completedstatus and a commit SHA. - Confirm the dialog. The confirmation message shows the short commit SHA you are rolling back to.
What happens during a rollback:
- ServerPlane reverts the app to the specified commit.
- Build and deploy commands run as usual.
- The app is restarted.
- A new deployment entry is created with the trigger set to Rollback.
Rollback does not revert your Git history. It restores the app to the specified commit. You can push new commits afterward and deploy them normally.
Tips
- If a deployment fails, check the logs in the Deployments tab to diagnose the issue. Common causes include failing build commands or missing dependencies.
- Rollback is only available for deployments where the commit SHA was recorded. Manual deploys and webhook-triggered deploys both record the commit SHA.
- Each rollback creates a new deployment entry, so you always have a complete audit trail.