必要な API を有効にします。サービス アカウントでログインした後、Google Developers Console の API ライブラリ ページで Google Cloud Testing API と Cloud Tool Results API を有効にします。これらの API を有効にするには、コンソール上部の検索ボックスに API 名を入力し、各 API の概要ページで [有効にする] をクリックします。
Jenkins をインストールして設定する
Jenkins CI は Linux または Windows 上でインストールと設定を行うことができます。このガイドの一部の情報は、Linux 上での Jenkins CI のインストールと実行に固有であり、ファイルパスにはスラッシュ（/）が含まれています。
Linux または Windows を実行している PC に Jenkins をダウンロードしてインストールするには、Jenkins のインストールの手順に沿って操作します。Jenkins をインストールした後、Jenkins の起動とアクセスの手順に沿って設定を完了し、Jenkins ダッシュボードにアクセスします。
グローバル セキュリティを設定する
Jenkins をインストールした時点では、ユーザー認証とアクセス制御が構成されていません。Firebase Test Lab と Jenkins を併用する前に、グローバル セキュリティを構成してアクセス制御とユーザー認証を実施します。
[null,null,["最終更新日 2025-08-16 UTC。"],[],[],null,["# Start testing with continuous integration (CI) systems\n\n\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---------------------------------------\n\nThis section describes how to use Test Lab with\n[Jenkins CI](http://jenkins-ci.org/).\n\n### Requirements\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\n### Install 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\n### Configure 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\n#### To 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\n### Create a Jenkins project\n\nNext, create a project for running continuous integration testing of your app\nwith Firebase Test Lab.\n\n#### To 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\n### Add 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\n#### Integrating 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\n#### Adding 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\n### Add 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\n#### To 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\n### Analyze 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--------------------------------------------\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."]]
