Mit Sammlungen den Überblick behalten
Sie können Inhalte basierend auf Ihren Einstellungen speichern und kategorisieren.
Mit den Funktionen für die kontinuierliche Integration (Continuous Integration, CI) von Looker können Sie Tests für Ihr LookML-Projekt ausführen, um zuverlässigere, effizientere und benutzerfreundlichere Daten zu liefern. Mit den CI-Validierungen können Sie Probleme mit SQL, Datentests, Inhalten und LookML erkennen, bevor sie in der Produktion auftreten. So können Sie Ihre LookML-Dateien überprüfen und Abfragefehler für Ihre Nutzer verhindern. Sie können die CI-Validatoren auch so konfigurieren, dass sie automatisch ausgeführt werden, wenn eine Pull-Anfrage für Ihr LookML-Repository gesendet wird.
CI besteht aus den folgenden Validatoren, die verschiedene Prüfungen für Ihre Looker-Instanz ausführen:
SQL-Validator: Hiermit wird geprüft, ob die Dimensionen in Ihren Explores korrekt für Ihre Datenbank ausgeführt werden.
Assert Validator: Führt alle von Ihren Looker-Entwicklern erstellten LookML-Datentests aus und gibt alle Fehler zurück.
Inhaltsvalidator: Führt die Inhaltsvalidierung von Looker aus, um nach Fehlern in den Looks und Dashboards in Ihrem LookML-Projekt zu suchen.
Wenn Sie diese Validatoren in Ihrer LookML-Instanz verwenden möchten, können Sie eine CI-Suite erstellen, in der eine Reihe von Validatoren und deren Optionen definiert sind, die Ihrem LookML-Projekt zugeordnet sind. Informationen zu CI-Suites finden Sie auf den folgenden Seiten:
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-09-05 (UTC)."],[],[],null,["| **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\nThe 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.\n\nCI is composed of the following validators, which run different checks against your Looker instance:\n\n- [SQL Validator](/looker/docs/ci-sql-validator) --- Verifies that the dimensions in your Explores run correctly against your database.\n- [Assert Validator](/looker/docs/ci-assert-validator) --- Runs any LookML [data tests](/looker/docs/reference/param-model-test) that were created by your Looker developers and returns all failures and errors.\n- [Content Validator](/looker/docs/ci-content-validator) --- Runs the Looker [content validation](/looker/docs/content-validation) to test for errors in the Looks and dashboards in your LookML project.\n- [LookML Validator](/looker/docs/ci-lookml-validator) --- Runs the [LookML Validator](/looker/docs/lookml-validation) to test for LookML errors in the project.\n\nTo 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:\n\n- [Creating a Continuous Integration suite](/looker/docs/ci-create-suite)\n- [Running Continuous Integration suites](/looker/docs/ci-run-suite)\n- [Viewing the results of a CI run](/looker/docs/ci-view-results)\n\nRequirements\n\nTo use Continuous Integration, you need the following:\n\n- A [Looker-hosted](/looker/docs/glossary#looker-hosted) instance that is [enabled for Continuous Integration](#enable-ci).\n\n | **Note:** For [Looker (Google Cloud core) instances](/looker/docs/looker-core-overview), Continuous Integration is supported for Public secure connections configurations only. Continuous Integration is not supported on Looker (Google Cloud core) instances that are enabled for [CMEK](/looker/docs/looker-core-cmek), or for instances configured with [Private connections](/looker/docs/looker-core-private-ip-overview) or Hybrid connections.\n- A Looker user account with at least one of the following permissions (both of these are included in the Admin [permission set](/looker/docs/admin-panel-users-roles#permission_sets)):\n\n - [`see_ci`](/looker/docs/admin-panel-users-roles#see_ci): required to view the results of CI runs, view the CI **Suites** page, and run CI suites.\n - [`manage_ci`](/looker/docs/admin-panel-users-roles#manage_ci): required to create CI suites, manage CI users, and configure the Git connection with Continuous Integration.\n\nEnabling Continuous Integration\n\nTo enable Continuous Integration, a Looker admin must perform the following tasks:\n\n- Enable the instance for Continuous Integration in the [**Continuous Integration** page](/looker/docs/admin-panel-platform-ci) of the Looker **Admin** panel.\n- Create a [Continuous Integration user](/looker/docs/admin-panel-platform-ci#ci-users).\n- [Install the CI GitHub app in your GitHub organization](/looker/docs/admin-panel-platform-ci#github). (This is highly recommended for all implementations, and required if you want to [use pull requests to trigger CI validation runs](/looker/docs/ci-create-suite#triggers))."]]
