Version Control and Rollbacks | Deployment History Guide

Keep all your deployment versions and instantly rollback if needed.

What is Version Control?#

Every time you deploy, a new version is created automatically.

You can:

  • View history - See all deployments
  • Compare versions - See what changed
  • Rollback - Go back to previous version
  • Delete versions - Remove old versions

Deployment History#

Viewing History#

Each deployment is recorded with:

  • Version number - Auto-incrementing ID
  • Deployment date - When deployed
  • Deployed by - Who made the deployment
  • Status - Success, in progress, failed
  • Notes - Custom deployment notes

Accessing History#

  1. Open Site Details
  2. Go to Versions or History tab
  3. See all deployments listed
  4. Newest version at top

Version Information#

Each version shows:

  • Build time - How long build took
  • Deployment time - When it went live
  • Files changed - What was updated
  • Status - Success or failed
  • Size - Total deployment size

Rollback to Previous Version#

Instantly go back to a working version.

Why Rollback?#

  • Deployment broke something - Go back to stable version
  • Content error - Wrong content deployed
  • Performance issue - New version is slow
  • Security issue - Found vulnerability
  • User complaints - Users report problems

Steps to Rollback#

  1. Go to Site Details
  2. Click Versions tab
  3. Find the version you want
  4. Click Rollback or Restore
  5. Confirm rollback
  6. Site reverts to that version

During Rollback#

  • Site becomes unavailable briefly
  • Files revert to previous state
  • CDN updates worldwide
  • Takes 1-5 minutes typically
  • You can monitor progress

After Rollback#

  1. Verify site works correctly
  2. Test key functionality
  3. Check for any issues
  4. Site should be stable again
  5. Note why you rolled back

Comparing Versions#

See what changed between versions.

What You Can Compare#

  • Files added - New files in new version
  • Files removed - Deleted from new version
  • Files changed - Modified files
  • Size difference - How much larger/smaller
  • Performance - Load time differences

How to Compare#

  1. Go to Versions tab
  2. Select two versions to compare
  3. Click Compare
  4. See differences highlighted
  5. Review changes in detail

Managing Versions#

Version Storage#

All versions are kept:

  • Automatic storage
  • No action needed
  • Accessible anytime
  • Can be deleted manually

Deleting Old Versions#

Free up space by deleting unused versions:

Steps:

  1. Go to Versions tab
  2. Find version to delete
  3. Click Delete or menu
  4. Confirm deletion
  5. Version is removed

Note: Cannot delete current active version

Keeping Important Versions#

Mark versions as important:

  • Won't be auto-cleaned
  • Easier to find later
  • Quick restoration

Deployment Strategies#

Blue-Green Deployment#

Test new version before switching:

  1. Blue (current) - Live version users see
  2. Green (new) - New version being tested
  3. Test - Verify green works
  4. Switch - Users see green now
  5. Keep blue - Easy rollback if needed

Canary Deployment#

Gradually roll out to users:

  1. Deploy to small percentage
  2. Monitor for issues
  3. Gradually increase percentage
  4. Rollback if problems found
  5. Full deployment when stable

Version Naming#

Auto-Generated Names#

Versions have automatic numbering:

  • Version 1, Version 2, etc.
  • Chronological order
  • Increment automatically

Custom Version Names#

You can name versions manually:

  1. During deployment, add version name
  2. Examples:
    • v1.2.3 - Semantic versioning
    • 2024-01-15 - Date-based
    • production-stable - Status-based
    • feature-login - Feature-based

Deployment Timeline#

Understanding the Timeline#

Timeline shows:

  • Date deployed - When it happened
  • Person who deployed - User name
  • Build duration - How long build took
  • Deployment status - Success/failed
  • File changes - What was in it

Finding Specific Version#

  1. Browse timeline
  2. Look for specific date
  3. Check who deployed it
  4. See what was deployed

Automatic Versioning#

How It Works#

  • Every deployment creates version automatically
  • No manual action needed
  • Versions numbered sequentially
  • Oldest versions can be deleted
  • Recent versions always kept

Retention Policy#

How long versions are kept:

  • Recent (7 days): All kept
  • 1 month old: Most kept
  • 3+ months old: Can be deleted
  • Critical versions: Keep indefinitely

Best Practices#

✓ Always test before deploying - Prevent need for rollback
✓ Keep at least 2-3 versions - Easy rollback access
✓ Name versions clearly - Easy identification
✓ Document deployments - Note what changed
✓ Monitor after deploy - Catch issues early
✓ Archive important versions - Keep long-term
✓ Regular cleanup - Delete very old versions
✓ Test rollback process - Know it works

Common Scenarios#

Scenario: Bug in New Version#

  1. User reports bug
  2. Check deployment history
  3. Find last stable version
  4. Click Rollback
  5. Site back to working state
  6. Fix bug locally
  7. Redeploy when fixed

Scenario: Content Error#

  1. Wrong content deployed
  2. Check version history
  3. Find correct version
  4. Restore that version
  5. Correct content shows
  6. Fix and redeploy

Scenario: Performance Drop#

  1. Users report slow site
  2. Check recent deployments
  3. Compare versions
  4. Find performance difference
  5. Rollback to faster version
  6. Investigate issue
  7. Deploy optimized version

Scenario: Planned Update#

  1. Plan new feature deployment
  2. Deploy to staging (version X)
  3. Test thoroughly
  4. Deploy to production (version Y)
  5. Monitor performance
  6. Keep version X available for rollback

Version Storage Limits#

Space Considerations#

  • Each version takes storage space
  • Old versions use less space
  • Can delete to free space
  • Backups automatically stored

Deleting to Save Space#

  1. Go to Versions
  2. Sort by date (oldest first)
  3. Delete versions over 3 months old
  4. Keep recent 5-10 versions
  5. Archive critical versions

Automation and CI/CD#

Continuous Deployment#

Automatically deploy on code push:

  1. Connect Git repository
  2. Every push creates version
  3. Build runs automatically
  4. Deploys if successful
  5. Rollback if failed

Version Naming in CI/CD#

Use commit hash or semantic versioning:

  • v1.2.3 from git tags
  • Commit hash: a1b2c3d
  • Branch name: main-2024-01-15
  • Timestamp: 20240115-143022

Related Topics#

Quick Reference#

TaskSteps
View versionsSite Details → Versions tab
RollbackSelect version → Click Rollback
Compare versionsSelect two → Click Compare
Delete old versionFind version → Click Delete
Name a versionDuring deployment, enter name
Check deployment dateLook at version timeline