trunk-io · TylerJang27 · Sep 15, 2026 · Sep 9, 2026 · Sep 9, 2026 · Sep 9, 2026
diff --git a/flaky-tests/detection/pass-on-retry-monitor.mdx b/flaky-tests/detection/pass-on-retry-monitor.mdx
@@ -49,7 +49,7 @@ You can create more than one pass-on-retry monitor for the same repository. Each
 
 A common pattern is to run one monitor scoped to stable branches (like `main`) with a shorter recovery period for fast feedback, and a second monitor scoped to `release/*` branches with a longer recovery period for builds where intermittent failures are more expensive to re-investigate.
 
-To add a monitor, navigate to **Settings** in the Trunk web app, open the repository, open the **Monitors** tab, and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted.
+To add a monitor, open the **Monitors** tab — on a [test collection](/flaky-tests/get-started/test-collections) or on a repository — and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted.
 
 <Frame caption="The Monitors tab lists each monitor as its own row, grouped into Health classification and Lifecycle & performance. Add Monitor creates an additional monitor in the same repository.">
 <img className="block dark:hidden" src="/assets/flaky-tests/detection/repo-monitors-tab-light.png" alt="The repository Monitors tab showing a pass-on-retry monitor, two failure-rate monitors, and lifecycle monitors, each as a separate row with an Add Monitor control." />

diff --git a/flaky-tests/get-started/ci-providers/atlassian-bamboo.mdx b/flaky-tests/get-started/ci-providers/atlassian-bamboo.mdx
@@ -86,6 +86,7 @@ Run Tests and Upload to Trunk:
           ./trunk-analytics-cli upload \
             --junit-paths "<XML_GLOB_PATH>" \
             --org-url-slug ${bamboo.TRUNK_ORG_URL_SLUG} \
+            --test-collection-id ${bamboo.TRUNK_TEST_COLLECTION_ID} \
             --token ${bamboo.TRUNK_API_TOKEN}
 
 variables:
@@ -119,6 +120,7 @@ Run Tests and Upload to Trunk:
           ./trunk-analytics-cli upload \
             --bazel-bep-path <BEP_JSON_PATH> \
             --org-url-slug ${bamboo.TRUNK_ORG_URL_SLUG} \
+            --test-collection-id ${bamboo.TRUNK_TEST_COLLECTION_ID} \
             --token ${bamboo.TRUNK_API_TOKEN}
 
 variables:
@@ -152,6 +154,7 @@ Run Tests and Upload to Trunk:
           ./trunk-analytics-cli upload \
             --xcresult-path <XCRESULT_PATH> \
             --org-url-slug ${bamboo.TRUNK_ORG_URL_SLUG} \
+            --test-collection-id ${bamboo.TRUNK_TEST_COLLECTION_ID} \
             --token ${bamboo.TRUNK_API_TOKEN}
 
 variables:

diff --git a/flaky-tests/get-started/ci-providers/azure-devops-pipelines.mdx b/flaky-tests/get-started/ci-providers/azure-devops-pipelines.mdx
@@ -74,6 +74,7 @@ steps:
     chmod +x trunk-analytics-cli
     ./trunk-analytics-cli upload --junit-paths "<XML_GLOB_PATH>" \
     --org-url-slug $(TRUNK_ORG_URL_SLUG) \
+    --test-collection-id $(TRUNK_TEST_COLLECTION_ID) \
     --token $(TRUNK_API_TOKEN)
   condition: always() # this should always run
   displayName: Upload test results to Trunk.io
@@ -93,6 +94,7 @@ steps:
     chmod +x trunk-analytics-cli
     ./trunk-analytics-cli upload --bazel-bep-path <BEP_JSON_PATH> \
     --org-url-slug $(TRUNK_ORG_URL_SLUG) \
+    --test-collection-id $(TRUNK_TEST_COLLECTION_ID) \
     --token $(TRUNK_API_TOKEN)
   condition: always() # this should always run
   displayName: Upload test results to Trunk.io
@@ -112,6 +114,7 @@ steps:
     chmod +x trunk-analytics-cli
     ./trunk-analytics-cli upload --xcresult-path <XCRESULT_PATH> \
     --org-url-slug $(TRUNK_ORG_URL_SLUG) \
+    --test-collection-id $(TRUNK_TEST_COLLECTION_ID) \
     --token $(TRUNK_API_TOKEN)
   condition: always() # this should always run
   displayName: Upload test results to Trunk.io
@@ -128,6 +131,7 @@ steps:
 
 - script: |
     TRUNK_ORG_URL_SLUG=$(TRUNK_ORG_URL_SLUG) \
+    TRUNK_TEST_COLLECTION_ID=$(TRUNK_TEST_COLLECTION_ID) \
     TRUNK_API_TOKEN=$(TRUNK_API_TOKEN) \
     bundle exec rspec
   displayName: Run RSpec tests and upload results to Trunk.io

diff --git a/flaky-tests/get-started/ci-providers/bitbucket-pipelines.mdx b/flaky-tests/get-started/ci-providers/bitbucket-pipelines.mdx
@@ -77,6 +77,7 @@ pipelines:
             chmod +x trunk-analytics-cli
             ./trunk-analytics-cli upload --junit-paths "**/junit.xml" \
               --org-url-slug $TRUNK_ORG_URL_SLUG \
+              --test-collection-id $TRUNK_TEST_COLLECTION_ID \
               --token $TRUNK_API_TOKEN
 ```
 ```yaml Bazel
@@ -97,6 +98,7 @@ pipelines:
             chmod +x trunk-analytics-cli
             ./trunk-analytics-cli upload --bazel-bep-path <BEP_JSON_PATH> \
               --org-url-slug $TRUNK_ORG_URL_SLUG \
+              --test-collection-id $TRUNK_TEST_COLLECTION_ID \
               --token $TRUNK_API_TOKEN
 ```
 ```yaml XCode
@@ -117,6 +119,7 @@ pipelines:
             chmod +x trunk-analytics-cli
             ./trunk-analytics-cli upload --xcresult-path <XCRESULT_PATH> \
               --org-url-slug $TRUNK_ORG_URL_SLUG \
+              --test-collection-id $TRUNK_TEST_COLLECTION_ID \
               --token $TRUNK_API_TOKEN
 ```
 ```yaml RSpec plugin
@@ -131,6 +134,7 @@ pipelines:
         script:
           - |
             TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG \
+            TRUNK_TEST_COLLECTION_ID=$TRUNK_TEST_COLLECTION_ID \
             TRUNK_API_TOKEN=$TRUNK_API_TOKEN \
             bundle exec rspec
 ```

diff --git a/flaky-tests/get-started/ci-providers/buildkite.mdx b/flaky-tests/get-started/ci-providers/buildkite.mdx
@@ -104,7 +104,7 @@ steps:
 ```yaml RSpec plugin
 steps:
   - label: Run Tests and Upload Results to Trunk.io
-    command: TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
+    command: TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_TEST_COLLECTION_ID=$TRUNK_TEST_COLLECTION_ID TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
     key: tests
 ```
 </CodeGroup>

diff --git a/flaky-tests/get-started/ci-providers/circleci.mdx b/flaky-tests/get-started/ci-providers/circleci.mdx
@@ -119,7 +119,7 @@ jobs:
     steps:
       - run:
           name: Run Tests and Upload Results to Trunk.io
-          command: TRUNK_ORG_URL_SLUG=${TRUNK_ORG_URL_SLUG} TRUNK_API_TOKEN=${TRUNK_API_TOKEN} bundle exec rspec
+          command: TRUNK_ORG_URL_SLUG=${TRUNK_ORG_URL_SLUG} TRUNK_TEST_COLLECTION_ID=${TRUNK_TEST_COLLECTION_ID} TRUNK_API_TOKEN=${TRUNK_API_TOKEN} bundle exec rspec
 ```
 </CodeGroup>
 

diff --git a/flaky-tests/get-started/ci-providers/droneci.mdx b/flaky-tests/get-started/ci-providers/droneci.mdx
@@ -129,7 +129,7 @@ steps:
       TRUNK_API_TOKEN:
         from_secret: TRUNK_API_TOKEN
     commands:
-      - TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
+      - TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_TEST_COLLECTION_ID=$TRUNK_TEST_COLLECTION_ID TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
 ```
 </CodeGroup>
 

diff --git a/flaky-tests/get-started/ci-providers/github-actions.mdx b/flaky-tests/get-started/ci-providers/github-actions.mdx
@@ -70,6 +70,7 @@ jobs:
         with:
           junit-paths: **/junit.xml        
           org-slug: <TRUNK_ORG_URL_SLUG>
+          test-collection-id: <TRUNK_TEST_COLLECTION_ID>
           token: ${{ secrets.TRUNK_API_TOKEN }}
 ```
 ```yaml XCResult Path
@@ -89,6 +90,7 @@ jobs:
         with:
           xcresult-path: ./test-results.xcresult        
           org-slug: <TRUNK_ORG_URL_SLUG>
+          test-collection-id: <TRUNK_TEST_COLLECTION_ID>
           token: ${{ secrets.TRUNK_API_TOKEN }}
 ```
 ```yaml Bazel BEP JSON
@@ -108,6 +110,7 @@ jobs:
         with:
           bazel-bep-path: ./build_events.json        
           org-slug: <TRUNK_ORG_URL_SLUG>
+          test-collection-id: <TRUNK_TEST_COLLECTION_ID>
           token: ${{ secrets.TRUNK_API_TOKEN }}
 ```
 ```yaml RSpec plugin
@@ -118,7 +121,7 @@ jobs:
 
     steps:
       - name: Run Tests and Upload Results to Trunk.io
-        run: TRUNK_ORG_URL_SLUG=${{ secrets.TRUNK_ORG_URL_SLUG }} TRUNK_API_TOKEN=${{ secrets.TRUNK_API_TOKEN }} bundle exec rspec
+        run: TRUNK_ORG_URL_SLUG=${{ vars.TRUNK_ORG_URL_SLUG }} TRUNK_TEST_COLLECTION_ID=${{ vars.TRUNK_TEST_COLLECTION_ID }} TRUNK_API_TOKEN=${{ secrets.TRUNK_API_TOKEN }} bundle exec rspec
 
 ```
 </CodeGroup>
@@ -160,6 +163,7 @@ Here's an example file.
 	      with:
 	        junit-paths: <TEST OUTPUT PATH>
 	        org-slug: my-trunk-org-slug
+	        test-collection-id: <TRUNK_TEST_COLLECTION_ID>
 	        token: ${{ secrets.TRUNK_API_TOKEN }}
 ```
 
@@ -185,6 +189,7 @@ This will override the response code of the test command. Make sure to set `cont
 	          junit-paths: <TEST OUTPUT PATH>
 	          run: <COMMAND TO RUN TESTS> # command to run tests goes here
 	          org-slug: my-trunk-org-slug
+	          test-collection-id: <TRUNK_TEST_COLLECTION_ID>
 	          token: ${{ secrets.TRUNK_API_TOKEN }}
 ```
 </Tab>
@@ -202,6 +207,7 @@ When quarantining is enabled, the `trunk-analytics-cli upload` command will **re
 |
     ./trunk-analytics-cli upload \
         --org-url-slug $TRUNK_ORG_URL_SLUG \
+        --test-collection-id $TRUNK_TEST_COLLECTION_ID \
         --token $TRUNK_API_TOKEN \
         --junit-paths $JUNIT_PATH
 ```
@@ -213,6 +219,7 @@ You can also wrap the test command with the Trunk Analytics CLI. When wrapping t
 ```bash
 ./trunk-analytics-cli test \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token $TRUNK_API_TOKEN \
     --junit-paths $JUNIT_PATH \
     --allow-empty-test-results \
@@ -281,6 +288,7 @@ jobs:
         with:
           junit-paths: <TEST OUTPUT PATH>
           org-slug: my-trunk-org-slug
+          test-collection-id: <TRUNK_TEST_COLLECTION_ID>
           token: ${{ secrets.TRUNK_API_TOKEN }}
         env:
           JOB_URL: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}/job/${{ steps.get-job-id.outputs.jobId }}
@@ -322,6 +330,7 @@ jobs:
         with:
           junit-paths: junit.xml
           org-slug: my-trunk-org-slug
+          test-collection-id: <TRUNK_TEST_COLLECTION_ID>
           token: ${{ secrets.TRUNK_API_TOKEN }}
         env:
           JOB_URL: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}/job/${{ steps.get-job-id.outputs.jobId }}

diff --git a/flaky-tests/get-started/ci-providers/gitlab.mdx b/flaky-tests/get-started/ci-providers/gitlab.mdx
@@ -119,7 +119,7 @@ stages:         # List of stages for jobs, and their order of execution
 unit_test_job:   # This job runs the tests and uploads the results to Trunk.io
   stage: test    
   script:
-    - TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
+    - TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_TEST_COLLECTION_ID=$TRUNK_TEST_COLLECTION_ID TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
 ```
 </CodeGroup>
 

diff --git a/flaky-tests/get-started/ci-providers/google-cloud-build.mdx b/flaky-tests/get-started/ci-providers/google-cloud-build.mdx
@@ -121,6 +121,7 @@ steps:
       ./trunk-analytics-cli upload \
         --junit-paths "<XML_GLOB_PATH>" \
         --org-url-slug <TRUNK_ORG_URL_SLUG> \
+        --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
         --token "${TRUNK_API_TOKEN}"
     waitFor:
       - run-tests
@@ -159,6 +160,7 @@ steps:
       ./trunk-analytics-cli upload \
         --bazel-bep-path bep.json \
         --org-url-slug <TRUNK_ORG_URL_SLUG> \
+        --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
         --token "${TRUNK_API_TOKEN}"
     waitFor:
       - run-tests

diff --git a/flaky-tests/get-started/ci-providers/jenkins.mdx b/flaky-tests/get-started/ci-providers/jenkins.mdx
@@ -115,7 +115,7 @@ pipeline {
   }
   stages {
     stage('Run Tests and Upload Results to Trunk.io'){
-      sh 'TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec'
+      sh 'TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_TEST_COLLECTION_ID=$TRUNK_TEST_COLLECTION_ID TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec'
     }
   }
 }

diff --git a/flaky-tests/get-started/ci-providers/otherci.mdx b/flaky-tests/get-started/ci-providers/otherci.mdx
@@ -40,6 +40,8 @@ You can find your token under **Settings** → **Organization** → **General**,
 
 Store the Trunk slug and API token obtained in the previous step in your CI provider as a secret, environment variable, or an equivalent concept and name them `TRUNK_ORG_URL_SLUG` and `TRUNK_API_TOKEN` respectively.
 
+Set `TRUNK_TEST_COLLECTION_ID` as well, to the ID of the [test collection](/flaky-tests/get-started/test-collections) the results belong to. It is not a secret, and it is per job rather than per organization — a job that uploads to a different collection sets a different value.
+
 ## Upload to Trunk
 
 Add an `Upload Test Results` step after running tests in each of your CI jobs that run tests. This should be minimally all jobs that run on pull requests, as well as from jobs that run on your main or [stable branches](../../detection/), for example,`main`, `master`, or `develop`.

diff --git a/flaky-tests/get-started/ci-providers/semaphoreci.mdx b/flaky-tests/get-started/ci-providers/semaphoreci.mdx
@@ -169,7 +169,7 @@ blocks:
       jobs:
         - name: Run Tests
           commands: 
-            - TRUNK_ORG_URL_SLUG=${TRUNK_ORG_URL_SLUG} TRUNK_API_TOKEN=${TRUNK_API_TOKEN} bundle exec rspec
+            - TRUNK_ORG_URL_SLUG=${TRUNK_ORG_URL_SLUG} TRUNK_TEST_COLLECTION_ID=${TRUNK_TEST_COLLECTION_ID} TRUNK_API_TOKEN=${TRUNK_API_TOKEN} bundle exec rspec
 ```
 </CodeGroup>
 

diff --git a/flaky-tests/get-started/ci-providers/travisci.mdx b/flaky-tests/get-started/ci-providers/travisci.mdx
@@ -96,7 +96,7 @@ dist: jammy
 node_js:
   - 20
 script:
-  - TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
+  - TRUNK_ORG_URL_SLUG=$TRUNK_ORG_URL_SLUG TRUNK_TEST_COLLECTION_ID=$TRUNK_TEST_COLLECTION_ID TRUNK_API_TOKEN=$TRUNK_API_TOKEN bundle exec rspec
 ```
 </CodeGroup>
 

diff --git a/flaky-tests/get-started/frameworks/android.mdx b/flaky-tests/get-started/frameworks/android.mdx
@@ -122,6 +122,7 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --junit-paths "./junit-reports/*.xml" \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 

diff --git a/flaky-tests/get-started/frameworks/bazel.mdx b/flaky-tests/get-started/frameworks/bazel.mdx
@@ -110,6 +110,7 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --bazel-bep-path=build_events.json \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 
@@ -120,6 +121,7 @@ If your test cases don't have file paths that can be matched against your CODEOW
 ```sh
 ./trunk-analytics-cli upload --bazel-bep-path=build_events.json \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN> \
     --use-bazel-target-for-codeowners
 ```

diff --git a/flaky-tests/get-started/frameworks/behave.mdx b/flaky-tests/get-started/frameworks/behave.mdx
@@ -96,10 +96,11 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --junit-paths "./junit-reports/*.xml" \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

diff --git a/flaky-tests/get-started/frameworks/cypress.mdx b/flaky-tests/get-started/frameworks/cypress.mdx
@@ -134,10 +134,11 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --junit-paths "./junit.xml" \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

diff --git a/flaky-tests/get-started/frameworks/dart-test.mdx b/flaky-tests/get-started/frameworks/dart-test.mdx
@@ -92,6 +92,7 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --junit-paths "./junit.xml" \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 

diff --git a/flaky-tests/get-started/frameworks/googletest.mdx b/flaky-tests/get-started/frameworks/googletest.mdx
@@ -98,6 +98,7 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --junit-paths "./junit.xml" \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 

diff --git a/flaky-tests/get-started/frameworks/gotestsum.mdx b/flaky-tests/get-started/frameworks/gotestsum.mdx
@@ -115,10 +115,11 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --junit-paths "./junit.xml" \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

diff --git a/flaky-tests/get-started/frameworks/gradle.mdx b/flaky-tests/get-started/frameworks/gradle.mdx
@@ -107,10 +107,11 @@ You make an upload to Trunk using the following command:
 ```sh
 ./trunk-analytics-cli upload --junit-paths "./app/build/test-results/test/*.xml" \
     --org-url-slug <TRUNK_ORG_URL_SLUG> \
+    --test-collection-id <TRUNK_TEST_COLLECTION_ID> \
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />