Rollback deployments in Firebase - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does 'rollback deployment' mean in Firebase hosting?

It means returning your website or app to a previous version that was working well, undoing the latest changes.

beginner

How can you rollback a Firebase hosting deployment?

Use the command firebase hosting:rollback followed by the site name and the version you want to restore.

beginner

Why is it important to keep track of deployment versions in Firebase?

Because it lets you quickly go back to a stable version if the new deployment causes problems.

beginner

What happens to your users when you rollback a Firebase deployment?

Users see the previous version of your site or app, as if the latest update never happened.

intermediate

Can you rollback multiple times in Firebase hosting?

Yes, you can rollback to any previous deployment version saved in Firebase hosting history.

Which Firebase CLI command is used to rollback a deployment?

A firebase hosting:restore

B firebase hosting:rollback

C firebase rollback:deploy

D firebase deploy:undo

The correct command to rollback a Firebase hosting deployment is firebase hosting:rollback.

What is the main reason to rollback a deployment?

A To fix issues caused by the latest deployment

B To update to a newer version

C To delete the site

D To add new features

Rollback is used to fix problems by returning to a previous stable version.

Can you rollback to any previous version in Firebase hosting?

A No, only the last deployment

B Only versions from the last 24 hours

C Yes, any saved deployment version

D Only versions manually saved

Firebase hosting keeps a history of deployments allowing rollback to any previous version.

What do users see after a rollback?

A The previous stable version

B An error page

C The latest deployment

D A blank page

Users see the previous stable version after rollback.

Is rollback a permanent deletion of the latest deployment?

A No, it archives the latest deployment

B Yes, it deletes the latest deployment

C Yes, it removes all deployment history

D No, it just switches the active version

Rollback switches the active version but keeps deployment history intact.

Explain how to perform a rollback deployment in Firebase hosting and why it might be necessary.

Think about the command and the reason for going back to an earlier version.

Describe what happens to your website and users when you rollback a Firebase deployment.

Focus on user experience and deployment state.

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