Manage rollouts and releases

If you have automatic rollouts enabled, every time you push a new commit to the live branch in your GitHub repository App Hosting automatically rolls out a new version of your app. You can check the rollout status in the Firebase console or in the App Hosting GitHub check.

Additionally, App Hosting supports manually triggered rollouts for CI/CD integration or any other case where you want to force a rollout.

View rollouts

The Firebase console provides access to detailed information about all rollouts of your app. In the App Hosting tab, select View dashboard for the backend whose rollouts you'd like to see. The dashboard displays information about the current rollout, along with a table listing a history of all rollouts for this backend.

Screen shot of the console rollouts view

Each rollout contains a git commit, a Cloud Build job, and a Cloud Run revision.

  • The git commit is the snapshot of your repository at the time the rollout is created.
  • The Cloud Build job is the build environment where App Hosting runs your app's build command. You can access Cloud Build logs by clicking on the build ID in the Firebase console.
  • The Cloud Run revision is the runtime environment for your Web app. You can learn more about a rollout's runtime configuration (things like CPU and memory limits and environment variables) by clicking the three-dot menu and selecting View Cloud Run revision.

Manually trigger a rollout

If you want to manually trigger a rollout from your GitHub source without pushing a new commit, you can create a rollout from the Firebase console or the Firebase CLI. This is useful for cases such as:

  • Forcing the regeneration of static content.
  • Allowing a CI/CD system to trigger rollouts.
  • Limiting production rollouts to specific dates or times.

To trigger a rollout in the Firebase console:

  1. In the App Hosting tab, select View dashboard for the backend you want to create a rollout for.
  2. In the backend dashboard, select Create rollout.
  3. Select the branch to deploy.
  4. Select the commit to deploy, either the latest commit or an earlier commit specified by its commit ID.
  5. Select Create. Status and a build number for the rollout is displayed in the rollout history table. When the rollout process is complete, this rollout is displayed as the current rollout.

To trigger a rollout in the Firebase CLI, run the following command and select the branch for the rollout when prompted:

firebase apphosting:rollouts:create BACKEND_ID

Alternatively, you can start a rollout for the latest commit for a specific branch by using the --git-branchoption:

firebase apphosting:rollouts:create BACKEND_ID
--git_branch BRANCH_NAME

You can also create a rollout with a specific commit using the --git-commit option:

firebase apphosting:rollouts:create BACKEND_ID
--git_commit COMMIT_ID

Change rollout settings

You can change the live branch for rollouts and disable or enable automatic rollouts using controls in the Settings > Deployment view in the dashboard for a backend.

  1. In the App Hosting tab, select View dashboard for the backend where you want to update rollout settings.
  2. In the backend dashboard, select Settings. The default view displays information about domains and custom domains.
  3. Select the Deployment view. In this view, you can change the live branch for rollouts and disable or enable automatic rollouts. Also, there are options to set the app root directory and the environment for the backend (see Deploy to multiple environments).