Rollbacks
How to rollback deployments to previous versions in Sproobo
Rollbacks allow you to quickly revert to a previous working version of your deployment if something goes wrong. Sproobo makes rollbacks simple and safe.
What are Rollbacks?
A rollback reverts your deployment to a previous version. Sproobo supports:
- One-click rollbacks to any previous deployment
- Automatic rollbacks on deployment failures
- Zero-downtime rollbacks using blue-green deployments
- Rollback history and audit logs
ℹ️
Rollbacks are instant and zero-downtime. Your application will continue serving traffic while rolling back.
Manual Rollbacks
- 1
Navigate to Deployment History
Go to Deployment → History to view all previous deployments.Navigate to Deployment History to see all previous deployments. - 2
View Deployment History
You'll see a list of all deployments with:- Deployment version and timestamp
- Commit hash and author
- Deployment status (success/failed)
- Duration and metrics
View all previous deployments with their status and details. - 3
Select Rollback Target
Choose which version you want to rollback to and click "Rollback".⚠️Make sure the target version was working correctly. You can view deployment logs and metrics to verify.
Select the deployment version you want to rollback to. - 4
Confirm Rollback
Review the rollback details and confirm:- Current version (will be replaced)
- Target version (will be deployed)
- Rollback type (instant or gradual)
Confirm the rollback operation. - 5
Monitor Rollback
Watch the rollback progress in real-time:- Rollback status and progress
- Health checks for new version
- Traffic switching status
Monitor the rollback progress and status.
Automatic Rollbacks
Sproobo can automatically rollback deployments that fail health checks:
- 1
Enable Automatic Rollback
Go to Deployment → Settings → Deployments and enable "Automatic Rollback on Failure".Enable automatic rollback for failed deployments. - 2
Configure Rollback Criteria
Set when automatic rollback should trigger:- Health Check Failures: Rollback if health checks fail after deployment
- Build Failures: Rollback if build fails (not applicable)
- Startup Failures: Rollback if deployment fails to start
- Error Rate: Rollback if error rate exceeds threshold
Configure when automatic rollback should trigger. - 3
Set Rollback Window
Configure how long to monitor before considering deployment successful:- Monitoring Period: Time to monitor after deployment (e.g., 5 minutes)
- Failure Threshold: Number of health check failures before rollback
Configure the rollback monitoring window and failure threshold.
Rollback Strategies
Sproobo supports different rollback strategies:
Rollback Types
- Instant Rollback: Immediately replace current version (zero-downtime)
- Gradual Rollback: Gradually shift traffic back to previous version
- Blue-Green Rollback: Keep both versions running during rollback
Rollback Safety
Safety Features
- Health Checks: Verify new version is healthy before switching
- Traffic Verification: Test rollback version before full traffic switch
- Audit Logs: All rollbacks are logged for compliance
- Rollback Protection: Prevent accidental rollbacks with confirmation
Rollback Best Practices
Best Practices
- Test rollbacks in staging before production
- Keep deployment history for easy rollback
- Tag stable versions for easy identification
- Monitor deployments after rollback
- Document rollback reasons and outcomes
- Use automatic rollbacks for critical deployments
Viewing Rollback History
- 1
Access Rollback History
Go to Deployment → History → Rollbacks to view all rollback events.View rollback history and events. - 2
Review Rollback Details
Each rollback entry shows:- Rollback timestamp and duration
- Source and target versions
- Rollback reason (manual or automatic)
- Rollback status and outcome
- User who triggered rollback (if manual)
Review detailed information about each rollback event.
Next Steps
Now that you know how to rollback deployments: