> [!WARNING]
> **Preview:** This product or feature is subject to the "Pre-GA Offerings Terms" in the [General Service Terms](https://cloud.google.com/terms/service-terms#1) section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see the [launch stage descriptions](https://cloud.google.com/products#product-launch-stages).
>
> If you encounter an issue during the Public Preview of Continuous Integration, report it using the [Looker Continuous Integration - Preview Issue Tracker form](https://docs.google.com/forms/d/e/1FAIpQLSed30eICYruU45R8WZQH6hIui28xtdDnejfetzpLHQ5PK0ZeA/viewform?usp=dialog).

The **Continuous Integration** page in the **Platform** section of the **Admin** menu lets you configure settings for the Looker [Continuous Integration (CI)](https://docs.cloud.google.com/looker/docs/2600/continuous-integration) feature.

> [!NOTE]
> **Note:** For [Looker (Google Cloud core) instances](https://docs.cloud.google.com/looker/docs/looker-core-overview), Continuous Integration is supported on instances that are configured with a Public IP network configuration. Continuous Integration is not supported on Looker (Google Cloud core) instances that are enabled for [CMEK](https://docs.cloud.google.com/looker/docs/looker-core-cmek), or on instances that are configured with a [private connections](https://docs.cloud.google.com/looker/docs/looker-core-private-ip-overview) or hybrid connections network configuration.

> [!WARNING]
> **Warning:** Don't enable Continuous Integration on a Looker instance that requires your data to reside in a specific location. Continuous Integration stores certain data in the United States.

## Enable Continuous Integration

The Looker [Continuous Integration (CI)](https://docs.cloud.google.com/looker/docs/2600/continuous-integration) feature lets you run tests on your LookML project to deliver more reliable, efficient, and user-friendly data experiences. You can use the CI validators to catch issues with SQL, data tests, content, and LookML before they hit production to verify your LookML and prevent query errors for your users. You can also configure the CI validators to run automatically when a pull request is submitted to your LookML repository.

A Looker admin can use the **Enable Continuous Integration** toggle to enable Continuous Integration on your instance.

## Integrations

If you use GitHub as a remote repository for your LookML project, you can configure Continuous Integration to [automatically run CI suites when LookML developers submit pull requests to your LookML repository](https://docs.cloud.google.com/looker/docs/2600/ci-create-suite#triggers). To automatically run CI suites on your repository, Continuous Integration needs the following permissions:

- Read access to your repository's metadata and pull requests
- Read and write access to your repository's commit statuses, repository hooks, and workflows

These permissions are not set up when you set up a Git connection for your LookML project in the Looker IDE. If you want to use pull request triggering for CI runs, your LookML project must be set up with a Git connection (as described on the [Setting up and testing a Git connection](https://docs.cloud.google.com/looker/docs/2600/setting-up-git-connection) page), and you must also configure the CI GitHub app as described in the [Configuring the CI GitHub app](https://docs.cloud.google.com/looker/docs/2600/admin-panel-platform-ci#configure-github) section.

### GitHub table

The **GitHub** table on the **Continuous Integration** Admin page lists the GitHub repositories that are configured for the LookML projects on your Looker instance. These GitHub repositories were configured by your LookML developers as described on the [Setting up and testing a Git connection](https://docs.cloud.google.com/looker/docs/2600/setting-up-git-connection) documentation page.

For each GitHub repository that's listed, the table shows whether the repository has been configured with the CI GitHub app:

- **Installed** : The repository has been granted the Looker CI GitHub application which enables [CI to be automatically run when LookML developers submit pull requests to your LookML repository](https://docs.cloud.google.com/looker/docs/2600/ci-create-suite#triggers).
- **Not Installed** : The repository hasn't been set up for pull request integration with Looker CI. To configure the repository for CI pull request integration, see the [Configuring the CI GitHub app](https://docs.cloud.google.com/looker/docs/2600/admin-panel-platform-ci#configure-github) section.

### Configuring the CI GitHub app

To grant the CI GitHub application for a repository, follow these steps:

1. On the **Continuous Integration** Admin page in Looker, click the **Configure GitHub App** button. This will open a browser window to the GitHub apps webpage.
2. Select the GitHub account where your LookML is stored.
3. In the **Repository access** section, select **All repositories** to allow CI integrations for all of the Git repositories owned by the resource owner, or select **Only select repositories** to choose the repositories with which you want to use Continuous Integration.
4. Click **Save**.

If the Looker CI GitHub application is successfully granted to the repository, Looker displays **Installed** for the repository in the [**GitHub** table](https://docs.cloud.google.com/looker/docs/2600/admin-panel-platform-ci#github-table) on the **Continuous Integration** Admin page.