Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dengan Continuous Integration (CI) Looker, jika Anda memicu peluncuran baru suite atau peluncuran ulang peluncuran CI sebelumnya secara manual, IDE Looker akan otomatis menampilkan halaman hasil peluncuran untuk peluncuran manual. Jika tidak, terlepas dari cara pengaktifan operasi, pengguna Looker dengan izin see_ci dapat mengakses hasil operasi dari halaman Runs di IDE Looker:
Halaman Runs mencantumkan CI yang berjalan untuk project LookML, beserta informasi berikut:
Status: Status operasi:
Dalam antrean: Proses berjalan menunggu proses CI lain selesai sebelum dimulai.
Berjalan: Validator yang ditentukan oleh suite CI sedang berjalan.
Lulus: Semua validator di suite CI berhasil diselesaikan dan tidak ada validator yang menampilkan error.
Gagal: Semua validator di suite CI berhasil diselesaikan dan setidaknya satu validator menampilkan error.
Error: Satu atau beberapa validator di suite CI gagal dijalankan.
Dibatalkan: Proses CI dibatalkan.
Suite: Nama suite CI.
Pemicu: Cara suite dipicu (manual, permintaan pull, atau API).
Status Git: Informasi tentang cabang atau commit yang divalidasi dalam proses:
Untuk operasi manual, nilainya adalah "Production" atau nama cabang pengembangan.
Untuk operasi yang dipicu oleh permintaan pull, nilainya adalah hyperlink ke SHA commit permintaan pull. Klik hyperlink SHA commit untuk membuka permintaan pull di tab browser lain.
Dipicu pada: Waktu CI dijalankan.
Hasil run CI
Di halaman Runs, klik tombol View Run untuk menjalankan CI guna melihat hasil validasinya:
Halaman hasil run untuk suite CI menampilkan informasi berikut:
Project LookML dan detail Git yang divalidasi oleh operasi (dan commit, untuk operasi yang dipicu oleh permintaan pull).
Informasi tentang CI yang dijalankan:
Cara dan waktu operasi dipicu.
Pengguna Looker yang memulai operasi (untuk operasi manual) atau cabang dan commit (untuk operasi yang dipicu oleh permintaan pull).
Waktu yang diperlukan untuk menyelesaikan CI.
Berapa lama waktu tunggu operasi dalam antrean sebelum dimulai.
Untuk validator yang menampilkan error, halaman hasil akan menampilkan setiap error, beserta pesan error dan link ke LookML, Jelajahi, atau konten sehingga Anda dapat menguji dan memperbaiki setiap error.
Untuk validator yang tidak menemukan error, halaman hasil akan menampilkan pesan berhasil.
Melihat hasil untuk validasi inkremental
Untuk validator CI yang dijalankan dan dikonfigurasi untuk validasi inkremental (untuk SQL Validator atau Content Validator), validator akan menampilkan error yang hanya ada di cabang pengembangan atau commit permintaan pull; validator yang diaktifkan untuk validasi inkremental tidak akan menampilkan error jika error sudah ada di versi produksi.
Berikut adalah contoh halaman hasil untuk validasi inkremental Validator SQL:
Halaman hasil menampilkan error yang hanya ada di cabang atau commit pengembangan.
Jika Eksplorasi tidak memiliki perubahan di cabang atau commit pengembangan, validator akan melewati Eksplorasi selama validasi. Jelajah ini ditandai dengan "Lewati" di hasil validator.
Validator yang dijalankan secara bertahap ditandai dengan "Inkremental" dalam hasil validasi.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-25 UTC."],[],[],null,["# Viewing the results of a CI run\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\nWith Looker Continuous Integration (CI), if you manually trigger a [new run of a suite](/looker/docs/ci-run-suite#manual-run) or a [rerun of a previous CI run](/looker/docs/ci-run-suite#manual-rerun), the Looker IDE automatically displays the run results page for the manual run. Otherwise, no matter how a run is triggered, a Looker user with the [`see_ci`](/looker/docs/admin-panel-users-roles#see_ci) permission can access the run results from the **Runs** page in the Looker IDE:\n\nThe **Runs** page lists the CI runs for the LookML project, along with the following information:\n\n- **Status** : The status of the run:\n - **Queued**: The run is waiting for another CI run to be completed before starting.\n - **Running**: The validators defined by the CI suite are running.\n - **Passed**: All of the validators in the CI suite were completed successfully and none of the validators returned an error.\n - **Failed**: All of the validators in the CI suite were completed successfully and at least one of the validators returned an error.\n - **Error**: One or more of the validators in the CI suite failed to run.\n - **Cancelled**: The CI run was cancelled.\n- **Suite**: The name of the CI suite.\n- **Trigger**: How the suite was triggered (manual, pull request, or API).\n- **Git state** : Information about the branch or commit that was validated in the run:\n - For manual runs, the value is either \"Production\" or the name of the development branch.\n - For runs triggered by a pull request, the value is a hyperlink to the commit SHA of the pull request. Click the commit SHA hyperlink to open the pull request in another browser tab.\n- **Triggered at**: The time that the CI run was initiated.\n\nCI run results\n--------------\n\nOn the **Runs** page, click the **View Run** button for a CI run to see its validation results:\n\nThe run results page for a CI suite shows the following information:\n\n1. The LookML project and Git details that the run validated (and the commit, for runs triggered by a pull request).\n2. Information about the CI run:\n - How and when the run was triggered.\n - The Looker user who initiated the run (for manual runs) or the branch and commit (for runs triggered by a pull request).\n - How long it took the CI run to be completed.\n - How long the run was waiting in the queue before beginning.\n3. For validators that return errors, the results page shows each error, along with the error message and links to the LookML, Explore, or content so that you can test and correct each error.\n4. For validators that found no errors, the results page shows a success message.\n\n### Viewing results for incremental validation\n\nFor CI validator runs configured for incremental validation (for the [SQL Validator](/looker/docs/ci-sql-validator#incremental_validation) or the [Content Validator](/looker/docs/ci-content-validator#incremental_validation)), the validator will return errors that exist only on the development branch or pull request commit; validators enabled for incremental validation won't return an error if the error already exists in the production version.\n\nThe following is an example of a results page for an incremental validation of the SQL Validator:\n\n1. The results page shows errors that exist only in the development branch or commit.\n2. If an Explore has no changes in the development branch or commit, the validator will skip the Explore during validation. These Explores are marked with \"Skipped\" in the validator results.\n3. The validators that were run incrementally are marked with \"Incremental\" in the validation results."]]
