Creating a Continuous Integration suite

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 permission can configure the following in a CI suite:

Before you begin

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

Creating a CI suite

You can configure and run the validators on the Suitespage in the Looker IDE:

To create a CI suite, follow these steps:

  1. From the Looker IDE , click the Continuous Integrationicon from the IDE navigation bar.
  2. Click the Suitestab to open the Suitespage.
  3. On the Suitespage, you can create a new suite or edit an existing suite:
    • To create a new suite, click the Create suitebutton.
    • To edit an existing suite, click the Edit suitebutton 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 Lookertoggle if you want to set up automatic validation testing whenever a Looker developer submits a pull request to your repository. See the 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 branchfield to specify that pull requests only to specific branches in the repository should trigger a run of the CI suite. See the 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:

  7. Save your changes:

    • If you are creating a new suite, click the Create suitebutton.
    • If you are editing an existing suite, click the Update suitebutton.

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 suitebutton on the Suitespage in the Looker IDE.
  • Manually, by rerunning a previous CI run , from the Runspage of the Looker IDE.

To configure a CI suite for automatic triggering on pull request, enable the Trigger on pull requests from Lookertoggle. To use pull request triggering, your Git repository must be configured by your Looker admin on the Continuous IntegrationAdmin page of Looker).

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

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 branchfield. 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 , click the Continuous Integrationicon from the IDE navigation bar.
  2. Click the Suitestab to open the Suitespage.
  3. On the Suitespage, click the Edit suitebutton for the suite.
  4. On the suite's page, click the Delete suitebutton.
  5. In the confirmation dialog, click the Delete suitebutton.
Create a Mobile Website
View Site in Mobile | Classic
Share by: