Rollback deployments in Firebase - Mini Project: Build & Apply

Rollback Deployments with Firebase Hosting

📖 Scenario: You are managing a website hosted on Firebase Hosting. Sometimes, after deploying new changes, you realize there is a problem and want to quickly go back to a previous working version.This project will guide you through setting up your Firebase Hosting project and learning how to rollback to a previous deployment.

🎯 Goal: Set up Firebase Hosting for a website and learn how to rollback to a previous deployment version using Firebase CLI commands.

📋 What You'll Learn

Initialize a Firebase Hosting project with a public directory

Deploy the website to Firebase Hosting

List previous deployments

Rollback to a previous deployment version

💡 Why This Matters

🌍 Real World

Websites often need quick fixes when new deployments cause issues. Rollbacks let you restore a stable version fast.

💼 Career

Knowing how to manage deployments and rollbacks is essential for cloud engineers and web developers working with Firebase Hosting.

1

Initialize Firebase Hosting Project

Create a Firebase Hosting project by running firebase init hosting and set the public directory to public. Then create a simple index.html file inside the public folder with the content <h1>Welcome to Firebase Hosting</h1>.

Firebase

# Run 'firebase init hosting' and create 'public/index.html' with the heading
# Your code here

Hint

Use the Firebase CLI to initialize hosting and create the public folder with an index.html file.

2

Deploy the Website to Firebase Hosting

Deploy your website by running the command firebase deploy --only hosting. This will upload your public folder content to Firebase Hosting.

Firebase

# Run 'firebase deploy --only hosting' to deploy your site
# Your code here

Hint

Use the Firebase CLI deploy command to publish your site.

3

List Previous Deployments

Use the command firebase hosting:versions:list to list all previous deployment versions for your Firebase Hosting site. This helps you find the version ID to rollback to.

Firebase

# Run 'firebase hosting:versions:list' to see previous deployment versions
# Your code here

Hint

Use the Firebase CLI to list deployment versions so you can choose one to rollback to.

4

Rollback to a Previous Deployment Version

Rollback your Firebase Hosting site to a previous deployment version by running firebase hosting:clone VERSION_ID, replacing VERSION_ID with the exact version ID you want to restore from the list.

Firebase

# Run 'firebase hosting:clone VERSION_ID' to rollback to a previous version
# Your code here

Hint

Replace VERSION_ID with the actual version ID from the list to rollback.

Practice

1.

What is the main purpose of firebase hosting:rollback?

easy

A. To deploy a new version of the website

B. To create a backup of the current deployment

C. To delete all hosting versions permanently

D. To undo a recent deployment and restore the previous version

Solution

1. Step 1: Understand rollback purpose

   Rollback is used to undo a deployment that caused issues by restoring the previous stable version.

2. Step 2: Identify command function

   The command firebase hosting:rollback specifically reverts to the last working deployment.

3. Final Answer:

   To undo a recent deployment and restore the previous version -> Option D

4. Quick Check:

   Rollback = undo deployment [OK]

Hint: Rollback means undo last deployment fast [OK]

Common Mistakes:

• Confusing rollback with deploying new versions
• Thinking rollback deletes all versions
• Assuming rollback creates backups

2.

Which of the following is the correct syntax to rollback the last Firebase Hosting deployment?

easy

A. firebase hosting:rollback

B. firebase rollback hosting

C. firebase deploy:rollback hosting

D. firebase hosting rollback --last

Solution

1. Step 1: Recall correct command structure

   The official Firebase CLI command for rollback is firebase hosting:rollback.

2. Step 2: Check option syntax

   Options B, C, and D do not match the correct Firebase CLI syntax for rollback.

3. Final Answer:

   firebase hosting:rollback -> Option A

4. Quick Check:

   Correct syntax = firebase hosting:rollback [OK]

Hint: Remember exact command: firebase hosting:rollback [OK]

Common Mistakes:

• Swapping command parts order
• Adding extra flags not needed
• Using deploy instead of hosting

3.

Given the deployment history shows versions v5, v6, and v7, with v7 currently live, what will firebase hosting:rollback do?

medium

A. Rollback to version v6

B. Rollback to version v7 again

C. Rollback to version v5

D. Delete all versions except v7

Solution

1. Step 1: Identify current live version

   The current live version is v7, the latest deployment.

2. Step 2: Understand rollback behavior

   Rollback reverts to the previous version before the current one, which is v6.

3. Final Answer:

   Rollback to version v6 -> Option A

4. Quick Check:

   Rollback = previous version v6 [OK]

Hint: Rollback always reverts to the immediate previous version [OK]

Common Mistakes:

• Choosing the oldest version instead of previous
• Thinking rollback redeploys current version
• Assuming rollback deletes versions

4.

You ran firebase hosting:rollback but got an error saying "No previous version found." What is the most likely cause?

medium

A. Firebase CLI is outdated

B. You have no prior deployments to rollback to

C. Your internet connection is down

D. You typed the command incorrectly

Solution

1. Step 1: Analyze error message meaning

   The error "No previous version found" means there is no earlier deployment saved to revert to.

2. Step 2: Consider possible causes

   This usually happens if this is the first deployment or all previous versions were deleted.

3. Final Answer:

   You have no prior deployments to rollback to -> Option B

4. Quick Check:

   No previous version = no rollback possible [OK]

Hint: No previous version means no rollback available [OK]

Common Mistakes:

• Assuming command syntax error
• Blaming network issues
• Ignoring deployment history

5.

You deployed version v10 but found a critical bug. You want to rollback to v9. However, v9 was deleted from the history. What is the best approach to recover your site quickly?

hard

A. Delete v10 and wait for Firebase to restore v9 automatically

B. Run firebase hosting:rollback to get v9 back

C. Redeploy a saved local copy of v9 manually

D. Contact Firebase support to restore v9

Solution

1. Step 1: Understand rollback limitations

   Rollback only works if the previous version exists in deployment history. Since v9 is deleted, rollback cannot restore it.

2. Step 2: Identify recovery method

   The best way is to redeploy a saved local copy of v9 manually to restore the stable version quickly.

3. Step 3: Evaluate other options

   Options B and C won't work because rollback needs the version present, and Firebase does not auto-restore deleted versions. Contact Firebase support to restore v9 may take too long for urgent fixes.

4. Final Answer:

   Redeploy a saved local copy of v9 manually -> Option C

5. Quick Check:

   Deleted version = manual redeploy needed [OK]

Hint: Rollback needs version history; redeploy local copy if missing [OK]

Common Mistakes:

• Expecting rollback to restore deleted versions
• Waiting for automatic Firebase restore
• Ignoring local backups