啟用必要的 API。使用服務帳戶登入後，請前往 Google Developers Console API 程式庫頁面，啟用 Google Cloud Testing API 和 Cloud Tool Results API。如要啟用這些 API，請在控制台頂端的搜尋框中輸入 API 名稱，然後在該 API 的「總覽」頁面上，按一下「啟用 API」。
安裝及設定 Jenkins
您可以在 Linux 或 Windows 上安裝及設定 Jenkins CI。本指南的某些詳細資料專用於在 Linux 上安裝及執行 Jenkins CI，包括在檔案路徑中使用斜線 (/)。
如要在執行 Linux 或 Windows 的電腦上下載及安裝 Jenkins，請按照「安裝 Jenkins」一文中的操作說明進行。安裝 Jenkins 後，請按照「啟動及存取 Jenkins」一文中的指示完成設定，並存取 Jenkins 資訊主頁。
設定全域安全性設定
首次安裝 Jenkins 時，系統不會設定使用者驗證和存取權控制項。將 Jenkins 與 Firebase Test Lab 搭配使用前，請先設定全域安全性設定，強制執行存取控管並驗證使用者。
[null,null,["上次更新時間：2025-08-16 (世界標準時間)。"],[],[],null,["\u003cbr /\u003e\n\nYou can use Firebase Test Lab when developing your app using any continuous\nintegration (CI) system. Continuous integration systems let you automatically\nbuild and test your app each time you check in updates to your app source code.\n\nUsing Firebase Test Lab with Jenkins CI\n\nThis section describes how to use Test Lab with\n[Jenkins CI](http://jenkins-ci.org/).\n\nRequirements\n\nBefore you can use Firebase Test Lab with Jenkins, you need to complete the\nfollowing steps:\n\n1. **Set up gcloud.** Follow the instructions from\n [Using Firebase Test Lab from the gcloud Command Line](/docs/test-lab/android/command-line)\n to create a Firebase project and configure your local Google Cloud SDK\n environment.\n\n2. **Create and authorize a service account.** Service accounts aren't subject\n to spam checks or captcha prompts, which could otherwise block your CI\n builds. Create a service account with an **Editor** role in the\n [Google Cloud console](https://console.cloud.google.com/iam-admin/serviceaccounts/)\n and then activate it\n (see the [gcloud auth activate-service-account documentation](https://cloud.google.com/sdk/gcloud/reference/auth/activate-service-account)\n to learn how).\n\n3. **Enable required APIs.** After logging in using the service account: In the\n [Google Developers Console API Library page](https://console.developers.google.com/apis/library),\n enable the **Google Cloud Testing API** and **Cloud Tool Results API** . To\n enable these APIs, type these API names into the search box at the top of the\n console, and then click **Enable API** on the overview page for that API.\n\nInstall and set up Jenkins\n\nYou can install and set up Jenkins CI on Linux or Windows. Certain details of\nthis guide are specific to installing and running Jenkins CI on Linux, including\nthe use of slashes (`/`) in file paths.\n\nTo download and install Jenkins on a computer running Linux or Windows, follow\nthe instructions on [Installing\nJenkins](https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins). After\ninstalling Jenkins, follow the instructions on\n[Starting and Accessing Jenkins](https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins)\nto complete setup and access the Jenkins dashboard.\n\nConfigure global security settings\n\nJenkins does not have user authentication and access control configured when it\nis first installed. Before using Jenkins with Firebase Test Lab, configure\nglobal security settings to enforce access control and authenticate\nusers.\n\nTo configure global security settings\n\n1. Navigate to the Jenkins dashboard on your server. To do this, browse to **http://\\\u003cservername\\\u003e:8080** , where **\\\u003cservername\\\u003e** is the name of the computer where you have installed Jenkins.\n2. On the Jenkins dashboard, click **Manage Jenkins** , and then click **Configure Global Security**.\n3. On the **Configure Global Security** page, click **Enable security** , and then click **Save**.\n\nFor more information about configuring security settings for Jenkins, see\n[Quick and Simple Security](https://wiki.jenkins-ci.org/display/JENKINS/Quick+and+Simple+Security),\n[Standard Security Setup](https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup),\nand\n[Securing Jenkins](https://wiki.jenkins-ci.org/display/JENKINS/Securing+Jenkins).\n\nCreate a Jenkins project\n\nNext, create a project for running continuous integration testing of your app\nwith Firebase Test Lab.\n\nTo create a Jenkins project\n\n1. Navigate to the Jenkins dashboard on your server. To do this, browse to **http://\\\u003cservername\\\u003e:8080** , where **\\\u003cservername\\\u003e** is the name of the computer where you have installed Jenkins.\n2. On the Jenkins dashboard, click **New Item**.\n3. Type a name for your project in the **Item name** field:\n - Choose **Freestyle project** to create a project that uses a single build configuration.\n - Choose **Build multi-configuration project** to create a project that runs on multiple different build configurations. If you plan to build your app with a variety of build configurations (multiple locales, multiple Android API levels, etc.), then a multi-configuration project is the best choice.\n4. Click **Save**.\n\nAfter your project is created, your web browser displays the main page for your\nproject.\n\nAdd revision control and Gradle build steps\n\nThis section describes how to integrate Jenkins with revision control systems\nsuch as GitHub, and how to add Gradle build steps to build APK packages\nfrom source code.\n\nIntegrating with GitHub and other revision control systems\n\nIf you use GitHub or another revision control system to manage the source code\nfor your app, you can configure Jenkins to run automated builds and run tests\neach time updates to your app are checked in. You can also configure\nJenkins to run builds periodically.\n\nTo learn about configuring builds in Jenkins, see\n[Configuring automatic builds](https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-Configuringautomaticbuilds).\n\nAdding Gradle build steps to rebuild APK packages\n\nIf you use a revision control system to manage source code for your app, you\nneed to include a Gradle build step to create new APK binaries each time Jenkins\ndownloads source code from your revision control system.\n\n1. Add a build step to run the following commands in the main directory for your\n application:\n\n ```\n ./gradlew :app:assembleDebug\n ./gradlew :app:assembleDebugAndroidTest\n ```\n\n \u003cbr /\u003e\n\n2. Add a build step to use the APK package(s) created by Gradle when testing\n with Test Lab. You can use this path as the\n **\\\u003clocal_server_path\\\u003e** in the shell script example provided below,\n where **\\\u003cAppFolder\\\u003e** is the Android Studio project folder for your\n app:\n\n ```\n \u003cAppFolder\u003e/app/build/outputs/apk\n ```\n\n \u003cbr /\u003e\n\nAdd Test Lab build steps to Jenkins\n\nNow you are ready to add a build step to Jenkins to run Test Lab using\nthe gcloud command line.\n\nTo add a gcloud build step\n\n1. From the main page for your project, click **Configure**.\n2. On the **project configuration** page, scroll down to the **Build** section,\n and then choose **Execute shell** from the **Add build step** menu.\n\n3. In the **Jenkins Execute shell command** window, enter the following,\n substituting **\\\u003clocal_server_path\\\u003e** for the path to the sample app on\n the server, **\\\u003capp_apk\\\u003e** for your app's APK, and\n **\\\u003capp_test_apk\\\u003e** for your app's test APK:\n\n ```\n gcloud firebase test android run --app \u003clocal_server_path\u003e/\u003capp_apk\u003e.apk\n --test \u003clocal_server_path\u003e/\u003capp_test_apk\u003e.apk\n ```\n\n \u003cbr /\u003e\n\nAnalyze test results\n\nAfter Test Lab completes testing of your app, you can review test\nresults in the Firebase console or in a\n[Google Cloud Storage](//cloud.google.com/storage/) bucket in\nyour project. You can also add a\n[`gsutil`](//cloud.google.com/storage/docs/gsutil) command to the\nshell command shown above to copy the test results data to your local computer.\nTo learn more, see\n[Analyzing Firebase Test Lab Results](/docs/test-lab/analyzing-results).\n\nContinuous integration with other CI systems\n\nTo learn how to use Firebase Test Lab with other CI systems, check out\ntheir docs:\n\n- [Bitrise](//devcenter.bitrise.io/testing/device-testing-for-android/)\n- [Circle CI](//circleci.com/docs/2.0/language-android/#testing-with-firebase-test-lab)\n\n| **Note:** If you create documentation explaining how to use Firebase Test Lab with another CI system, [contact us](mailto:cloud-test-lab-integration@google.com) so that we can review it for inclusion in this section."]]
