Rollbacks
Roll back deployments to previous versions
Sometimes you need to quickly revert a change to your installation without waiting for a full build cycle of pushing a new commit. When you have a previous deployment you wish to make live again, Ryvn lets you quickly roll back to that deployment.
Rolling Back a Deployment
To roll back a deployment:
Navigate to Environments
Select Environment
Select Installation
Access Activity Tab
Initiate Rollback
- Find the successful deployment you want to roll back to 2. Click the Rollback button next to that deployment
- Confirm the rollback in the dialog
What Gets Rolled Back
The following configuration items are included in a rollback:
Configuration | Rolled Back? | Details |
---|---|---|
Run Command | ✓ | Command used to start your application |
Health Check Path | ✓ | Path and configuration for health checks |
Docker Command | ✓ | Commands for Docker-based deployments |
Build Assets | ✓ | Built artifacts from the deployment |
Number of Replicas | ✓ | Scaling configuration from the deployment |
Environment Variables | ✓ | Custom environment variables |
Persistent storage volumes are stateful between deployments and cannot be rolled back. Make sure your application can handle any data schema changes when rolling back.
Build Retention
Ryvn retains rollback capability for your most recent deployments. The number of previous builds available for rollback depends on your plan.
Automatic Deployments
If automatic deployments are enabled for your installation, rolling back will automatically disable auto-deploy. You can re-enable auto-deploy in your installation’s Settings tab after the rollback.
After Rolling Back
Monitor your application through the Ryvn Dashboard to ensure:
- The rollback completed successfully
- Your application is running as expected
- All health checks are passing
For registry-based deployments, Ryvn will use the specific image and digest from the previous deployment. If that image is no longer available in your registry, the rollback will fail.