> [!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).

A Continuous Integration (CI) suite is a set of validation instructions that is associated with your LookML project. A Looker user with the [`manage_ci`](https://docs.cloud.google.com/looker/docs/2600/admin-panel-users-roles#manage_ci) permission can configure the following in a CI suite:

- How a CI validation run is triggered ([manually from the Looker IDE](https://docs.cloud.google.com/looker/docs/2600/ci-run-suite#manual-run) or [automatically when a pull request is submitted to your repository](https://docs.cloud.google.com/looker/docs/2600/ci-run-suite#pr-run)).
- Which CI validators to run.
- Additional options for each validation test. See the documentation pages for each of the validators for details:
  - [SQL Validator](https://docs.cloud.google.com/looker/docs/2600/ci-sql-validator)
  - [Assert Validator](https://docs.cloud.google.com/looker/docs/2600/ci-assert-validator)
  - [Content Validator](https://docs.cloud.google.com/looker/docs/2600/ci-content-validator)
  - [LookML Validator](https://docs.cloud.google.com/looker/docs/2600/ci-lookml-validator)

## Before you begin

Before you can create a CI suite, you need the following:

- A Looker instance that meets the [requirements for CI](https://docs.cloud.google.com/looker/docs/2600/continuous-integration#requirements) and that is [enabled for CI](https://docs.cloud.google.com/looker/docs/2600/continuous-integration#enable-ci).
- A Looker user account with the [`manage_ci`](https://docs.cloud.google.com/looker/docs/2600/admin-panel-users-roles#manage_ci) permission (this permission is included in the Admin [permission set](https://docs.cloud.google.com/looker/docs/2600/admin-panel-users-roles#permission_sets)).

## Creating a CI suite

You can configure and run the validators on the **Suites** page in the Looker IDE:

![](https://docs.cloud.google.com/static/looker/docs/images/ci-suites-page-updated-2506.png)

To create a CI suite, follow these steps:

1. From the [Looker IDE](https://docs.cloud.google.com/looker/docs/2600/looker-ide), click the **Continuous Integration** icon from the IDE navigation bar.
2. Click the **Suites** tab to open the **Suites** page.
3. On the **Suites** page, you can create a new suite or edit an existing suite:
   - To create a new suite, click the **Create suite** button.
   - To edit an existing suite, click the **Edit suite** button for the suite.
4. Enter a name for the **Suite name**. If you are editing an existing suite, you can optionally click the pencil icon to edit the suite name.
5. (Optional) Enable the **Trigger on pull requests from Looker** toggle if you want to set up automatic validation testing whenever a Looker developer submits a pull request to your repository. See the [Triggers](https://docs.cloud.google.com/looker/docs/2600/ci-create-suite#triggers) section of this page for more information.

   If you enable pull request triggering for a CI suite, you can optionally use the **Only for target branch** field to specify that pull requests only to specific branches in the repository should trigger a run of the CI suite. See the [Triggers](https://docs.cloud.google.com/looker/docs/2600/ci-create-suite#triggers) section of this page for more information.
6. Optionally, enable the validator toggles to turn on a validator and configure its options. See the documentation pages for each of the validators for details:

   - [SQL Validator](https://docs.cloud.google.com/looker/docs/2600/ci-sql-validator)
   - [Assert Validator](https://docs.cloud.google.com/looker/docs/2600/ci-assert-validator)
   - [Content Validator](https://docs.cloud.google.com/looker/docs/2600/ci-content-validator)
   - [LookML Validator](https://docs.cloud.google.com/looker/docs/2600/ci-lookml-validator)
7. Save your changes:

   - If you are creating a new suite, click the **Create suite** button.
   - If you are editing an existing suite, click the **Update suite** button.

### Triggers

CI runs can be triggered in several ways:

- Automatically, when a pull request is submitted to your LookML project's repository by a Looker developer.
- Manually, [using the **Run suite** button](https://docs.cloud.google.com/looker/docs/2600/ci-run-suite#manual-run) on the **Suites** page in the Looker IDE.
- Manually, by [rerunning a previous CI run](https://docs.cloud.google.com/looker/docs/2600/ci-run-suite#manual-rerun), from the **Runs** page of the Looker IDE.

To configure a CI suite for automatic triggering on pull request, enable the **Trigger on pull requests from Looker** toggle. To use pull request triggering, your Git repository must be configured by your Looker admin on the [**Continuous Integration** Admin](https://docs.cloud.google.com/looker/docs/2600/admin-panel-platform-ci#github) page of Looker).

> [!TIP]
> **Tip:** Even if you configure the CI suite to run automatically on pull requests, you can still initiate a [manual run](https://docs.cloud.google.com/looker/docs/2600/ci-run-suite#manual-run) or [manually rerun a previous run](https://docs.cloud.google.com/looker/docs/2600/ci-run-suite#manual-rerun) of the CI suite from the Looker IDE.


If you enable pull request triggers for a CI suite, you can optionally specify that pull requests only to specific branches in the repository should trigger a run of the CI suite. To limit automatic pull request triggers of CI runs to specific branches in your repository, enter a comma-separated list of the branches in the **Only for target branch** field.

For example, if a repository has three branches named `main`, `release_1`, and `dev`, you can enter `main, release_1` in the **Only for target branch** field. This means that CI runs will be triggered when a Looker developer submits a pull request to either the `main` or the `release_1` branch. If a Looker developer submits a pull request to the `dev` branch, this won't trigger an automatic run of the CI suite.

## Deleting a suite

To delete a CI suite, perform the following steps:

1. From the [Looker IDE](https://docs.cloud.google.com/looker/docs/2600/looker-ide), click the **Continuous Integration** icon from the IDE navigation bar.
2. Click the **Suites** tab to open the **Suites** page.
3. On the **Suites** page, click the **Edit suite** button for the suite.
4. On the suite's page, click the **Delete suite** button.
5. In the confirmation dialog, click the **Delete suite** button.