Preview: This product or feature is subject to the "Pre-GA Offerings Terms" in theGeneral Service Terms section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

If you encounter an issue during the Public Preview of Continuous Integration, report it using theLooker Continuous Integration - Preview Issue Tracker form.

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, 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.

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

• SQL Validator — Verifies that the dimensions in your Explores run correctly against your database.
• Assert Validator — Runs any LookMLdata tests that were created by your Looker developers and returns all failures and errors.
• Content Validator — Runs the Lookercontent validation to test for errors in the Looks and dashboards in your LookML project.
• LookML Validator — Runs theLookML Validator to test for LookML errors in the project.

To use these validators on your LookML instance, you can create aCI 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
• Running Continuous Integration suites
• Viewing the results of a CI run

Requirements

To use Continuous Integration, you need the following:

• ALooker-hosted instance that isenabled for Continuous Integration.

  Note: ForLooker (Google Cloud core) instances, Continuous Integration is supported for Public secure connections configurations only. Continuous Integration is not supported on Looker (Google Cloud core) instances that are enabled forCMEK, or for instances configured withPrivate connections or Hybrid connections.

• A Looker CI user account. Looker CI users are created automatically for Looker instances that have beenenabled for Continuous Integration. Looker CI users are created in theLooker CI Users user group with theLooker CI Users role. A Looker admin can view the Looker CI users from theService Accounts tab of theUsers Admin page.

Enabling Continuous Integration

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

• Enable the instance for Continuous Integration in theContinuous Integration page of the LookerAdmin panel.
• Install the CI GitHub app in your GitHub organization. (This is highly recommended for all implementations, and required if you want touse pull requests to trigger CI validation runs).