[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# Running Continuous Integration suites\n\n| **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).\n|\n| 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).\n\nContinuous Integration (CI) runs can be triggered in several ways:\n\n- [Automatically](#pr-run) when a pull request is submitted to your LookML project's repository by a Looker developer (see the [Creating a Continuous Integration suite](/looker/docs/ci-create-suite#triggers) page for information on setting this up).\n- [Manually triggering a new run of a CI suite](#manual-run) from the Looker IDE.\n- [Manually re-running a previous CI run](#manual-rerun) from the Looker IDE.\n\nOnce the validation tests have completed, you can review the results, as described on the [Viewing Continuous Integration run results](/looker/docs/ci-view-results) documentation page.\n\nAutomatic triggering from pull requests\n---------------------------------------\n\nIf you have enabled your CI suite with [**Trigger on pull requests from Looker**](/looker/docs/ci-create-suite#triggers), CI will trigger a validation run automatically when a Looker developer submits a pull request to your LookML repository. (You can optionally specify that pull requests only to [certain branches in your repository](/looker/docs/ci-create-suite#target-branches) should trigger automatic CI runs.)\n\nFor automatic pull request validation runs, CI validates the latest pull request commit and returns all of the errors in that version of the repository.\n| **Note:** For validators in the CI suite that are configured to perform incremental validation, the validator will return errors that exist only on the pull request commit itself; validators enabled for incremental validation won't return an error if it already exists in the production version. See the [SQL Validator](/looker/docs/ci-sql-validator#incremental_validation) or [Content Validator](/looker/docs/ci-content-validator#incremental_validation) documentation for more information on incremental validation.\n\nSee the [Viewing Continuous Integration run results](/looker/docs/ci-view-results) documentation page for information on viewing the results.\n\nManually triggering a new run of a CI suite\n-------------------------------------------\n\nA Looker user with the [`see_ci`](/looker/docs/admin-panel-users-roles#see_ci) permission can manually trigger a CI run from the Looker IDE.\n\nTo manually trigger a new run of a CI suite, follow these steps:\n\n1. From the [Looker IDE](/looker/docs/looker-ide), click the **Continuous Integration** icon from the IDE navigation bar.\n2. Click **Suites** to open the **Suites** page.\n3. Click the **Run suite** button for the CI suite that you want to run (if you don't have any CI suites for your project, you can [create a CI suite](/looker/docs/ci-create-suite)).\n4. In the **Trigger a run manually** dialog, use the **Workspace** options to select the branch that you want to validate (see the [Workspace](#workspace) section for details):\n\n - To validate the production version of your LookML project, click **Production**.\n - If you want to validate a development branch of your LookML project, click **Dev Mode** . Use the **Branch** pull-down menu to select which development branch to validate.\n5. To trigger the run of the CI suite, click **Start run**.\n\nThe CI suite may take several minutes to complete running, depending on the size of your project, the validators that are included in the CI suite, and the configuration of the CI suite.\n\nAfter you trigger a run, the Looker IDE will display the **Run** page for the suite that you triggered. Once the validation tests are completed, the **Run** page will show the results for each of the validators. You can navigate away from the **Run** page while the validation tests are running, and then later return to the **Run** page to see the results.\n\nSee the [Viewing Continuous Integration run results](/looker/docs/ci-view-results) documentation page for information on viewing the results.\n\n### Workspace\n\nWhen you manually trigger a CI run, you can use the **Workspace** options to validate either the production version of your repository or a development branch of your repository.\n\nFor the **Production** option, if you want to identify which branch or commit is used for the production version, you can look in the Looker IDE in the **Default Production Branch** field of the **Git Summary** section of the [**Branch Management**](/looker/docs/version-control-and-deploying-changes#managing_git_branches) page of the **Project Settings**:\n\n- For projects configured with [advanced deploy mode](/looker/docs/advanced-deploy-mode), the production version is a commit or tag that is selected in the [deployment manager](/looker/docs/advanced-deploy-mode#deployment_manager) by a Looker developer who has the [`deploy` permission](/looker/docs/admin-panel-users-roles#deploy).\n- For projects without advanced deploy mode, the production version is the branch configured in the **Git Production Branch Name** field in the **Project Configuration** page of the [**Project Settings**](/looker/docs/git-options#project_settings).\n\nFor the **Dev Mode** option, note the following for validating development branches in your project:\n\n- To see the branches in your LookML project and to identify the production branch and the personal branches of your developers, refer to the [**Branch Management**](/looker/docs/version-control-and-deploying-changes#managing_git_branches) page of the **Project Settings** of your project in the Looker IDE.\n- To validate a development branch, the development branch must be pushed to your LookML repository. In the Looker IDE, that means the developer must click the [**Commit Changes \\& Push**](/looker/docs/git-command-reference#commit) button or select the **Commit** option from the [Git Actions panel](/looker/docs/git-command-reference) in the IDE.\n\nManually re-running a previous CI run\n-------------------------------------\n\nFor runs that have finished (if the run passed, failed, errored, or was cancelled), a Looker user with the [`see_ci`](/looker/docs/admin-panel-users-roles#see_ci) permission can manually trigger a rerun of the CI run from the Looker IDE:\n\n- If you rerun a PR-triggered run, Continuous Integration runs against the same commit as the original run.\n- If you rerun a manually-triggered run, Continuous Integration runs against the production state or branch HEAD *at the time of the rerun*, which will include any subsequents commits that were made since the initial CI run.\n\nIn addition, if you have edited the CI suite since the initial run, a rerun will include any changes that you made to the CI suite since the initial run.\n\nTo rerun a CI run, follow these steps:\n\n1. From the [Looker IDE](/looker/docs/looker-ide), click the **Continuous Integration** icon from the IDE navigation bar.\n2. Click **Runs** to open the **Runs** page.\n3. On the **Runs** page, click the **View Run** button for the CI run you want to cancel.\n4. On the run results page for the selected run, click the **Rerun** button at the top of the page.\n\nOnce you click **Rerun** , the Content Validator will initiate the run and return you to the **Run** page for the new run.\n\nSee the [Viewing Continuous Integration run results](/looker/docs/ci-view-results) documentation page for information on viewing the results.\n\nCancelling a CI run\n-------------------\n\nIf you want to cancel a CI run that is running, you can do so from its **Run** page by following these steps:\n\n1. From the [Looker IDE](/looker/docs/looker-ide), click the **Continuous Integration** icon from the IDE navigation bar.\n2. Click **Runs** to open the **Runs** page.\n3. On the **Runs** page, click the **View Run** button for the CI run you want to cancel.\n4. On the **Run** page for the selected run, click the **Cancel** button at the top of the page.\n\nOnce you click **Cancel** , Continuous Integration will cancel the run display the **Cancelled** status on the **Run** page."]]