> [!NOTE]
> **Note:** Looker's Continuous Integration is based on the legacy standalone Spectacles service. Looker will continue to integrate and evolve the Spectacles features into Looker's Continuous Integration, and the legacy standalone Spectacles service itself will be discontinued starting November 30, 2026. Existing Spectacles customers will receive an email with details. If you have any questions or require assistance, please contact us at [spectacles-support@google.com](mailto:spectacles-support@google.com).

The **Looker Continuous Integration (CI)** features let 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, LookML, and coding style 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 or to an imported LookML project, on a schedule, or when a dbt Cloud CI job finishes.

CI is composed of the following validators, which run different checks against your Looker instance:

- [SQL Validator](https://docs.cloud.google.com/looker/docs/2622/ci-sql-validator.md.txt) --- Verifies that the dimensions in your Explores run correctly against your database.
- [Assert Validator](https://docs.cloud.google.com/looker/docs/2622/ci-assert-validator.md.txt) --- Runs any LookML [data tests](https://docs.cloud.google.com/looker/docs/2622/reference/param-model-test) that were created by your Looker developers and returns all failures and errors.
- [Content Validator](https://docs.cloud.google.com/looker/docs/2622/ci-content-validator.md.txt) --- Runs the Looker [content validation](https://docs.cloud.google.com/looker/docs/2622/content-validation.md.txt) to test for errors in the Looks and dashboards in your LookML project.
- [LookML Validator](https://docs.cloud.google.com/looker/docs/2622/ci-lookml-validator.md.txt) --- Runs the [LookML Validator](https://docs.cloud.google.com/looker/docs/2622/lookml-validation.md.txt) to test for LookML errors in the project.
- [Style Validator](https://docs.cloud.google.com/looker/docs/2622/ci-style-validator.md.txt) --- Enforces LookML coding standards, naming conventions, and structural best practices across your project.

To use these validators on your LookML instance, you can create a *CI suite*, which defines a set of validators and their options that are associated with your LookML project. See the following pages for information on CI suites:

- [Creating a Continuous Integration suite](https://docs.cloud.google.com/looker/docs/2622/ci-create-suite.md.txt)
- [Running Continuous Integration suites](https://docs.cloud.google.com/looker/docs/2622/ci-run-suite.md.txt)
- [Viewing the results of a CI run](https://docs.cloud.google.com/looker/docs/2622/ci-view-results.md.txt)

## Requirements

To use CI, you need the following:

- A [Looker-hosted](https://docs.cloud.google.com/looker/docs/2622/glossary.md.txt#looker-hosted) instance that is [enabled for CI](https://docs.cloud.google.com/looker/docs/2622/continuous-integration.md.txt#enable-ci).

  > [!NOTE]
  > **Note:** For [Looker (Google Cloud core) instances](https://docs.cloud.google.com/looker/docs/looker-core-overview.md.txt), CI is supported on instances that are configured with [public secure connections](https://docs.cloud.google.com/looker/docs/looker-core-networking-options.md.txt#public_ip_connections) or with [private connections](https://docs.cloud.google.com/looker/docs/looker-core-networking-options.md.txt#private_ip_connections) or [hybrid connections](https://docs.cloud.google.com/looker/docs/looker-core-networking-options.md.txt#private-ip-public-ip) that use [Private Service Connect](https://docs.cloud.google.com/looker/docs/looker-core-networking-options.md.txt#psc). In addition, CI is supported on Looker (Google Cloud core) instances that are enabled for [CMEK](https://docs.cloud.google.com/looker/docs/looker-core-cmek.md.txt) or that are within a [VPC Service Controls perimeter](https://docs.cloud.google.com/looker/docs/looker-core-vpcsc.md.txt). CI is not supported on Looker (Google Cloud core) instances that are configured with private connections or hybrid connections that use [private services access](https://docs.cloud.google.com/looker/docs/looker-core-networking-options.md.txt#psa). To use the [CI GitHub app](https://docs.cloud.google.com/looker/docs/2622/admin-panel-platform-ci.md.txt#github) or the [dbt Cloud integration](https://docs.cloud.google.com/looker/docs/2622/admin-panel-platform-ci.md.txt#dbt-cloud) on an instance that uses private connections, hybrid connections, or a VPC Service Controls perimeter, you must update your networking configuration to allow ingress and egress traffic to and from GitHub and your dbt Cloud host URL.

- A Looker CI user account. When you enable CI on your instance, Looker automatically creates 10 Looker CI users in the [**Looker CI Users** user group](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-groups.md.txt#ci-users) with the [**Looker CI Users** role](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-roles.md.txt#ci-users). A Looker admin can view the Looker CI users from the **Service Accounts** tab of the [**Users**](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-users.md.txt) Admin page.

## Compliance capabilities of CI

Looker CI is not included in the [FedRAMP High, FedRAMP Moderate, or DoD Impact Level 5 (IL5) authorization boundaries](https://docs.cloud.google.com/assured-workloads/docs/control-packages.md.txt#regulatory-data-boundaries).

Prior to enabling the Looker CI setting for your Looker instance, consult with your authorizing body to determine whether Looker CI's compliance offerings meet your organization's specific security and regulatory requirements.

For Looker (Google Cloud core) instances, each [Assured Workloads control package](https://docs.cloud.google.com/assured-workloads/docs/control-packages.md.txt) that becomes available will add Looker CI features as default offerings as that package's change requirements and processes are met.

## Enabling CI

To enable CI, a Looker admin must perform the following tasks:

- Enable the instance for CI in the [**Continuous Integration** page](https://docs.cloud.google.com/looker/docs/2622/admin-panel-platform-ci.md.txt) of the Looker **Admin** panel.
- [Install the CI GitHub app in your GitHub organization](https://docs.cloud.google.com/looker/docs/2622/admin-panel-platform-ci.md.txt#github). (This is highly recommended for all implementations, and required if you want to use pull requests from [your LookML project](https://docs.cloud.google.com/looker/docs/2622/ci-create-suite.md.txt#pr-trigger) or [imported LookML projects](https://docs.cloud.google.com/looker/docs/2622/ci-create-suite.md.txt#imported-project-trigger) to trigger CI validation runs).