> ## Documentation Index > Fetch the complete documentation index at: https://docs.trunk.io/llms.txt > Use this file to discover all available pages before exploring further. # Atlassian Bamboo > Configure Atlassian Bamboo to upload test results to Trunk Flaky Tests Trunk Flaky Tests integrates with your CI by adding a step in your Bamboo Plans to upload tests with the [Trunk Analytics CLI](../../reference/cli-reference). **Not using GitHub for source control?** Flaky Test support for source control providers like GitLab and BitBucket is still experimental. If you're using a source control provider other than GitHub, [**contact us**](mailto:support@trunk.io) **to get started**. Before you start on these steps, see the [Test Frameworks](../frameworks/) docs for instructions on producing a Trunk-compatible output for your test framework. ## Setup steps Work through the steps below in order. Once you've finished the last one, you're set up — head to [app.trunk.io](https://app.trunk.io) to see your results. Get your Trunk organization slug and token} /> Set your slug and token as a variable in CI} /> Configure your CI to upload to Trunk} /> Validate your uploads in Trunk} /> ## Trunk Organization Slug and Token Before setting up uploads to Trunk, you must sign in to [app.trunk.io](https://app.trunk.io/login?intent=flaky%20tests) and obtain your Trunk organization slug and token. ### Trunk Slug You can find your organization slug under **Settings** → **Organization** → **General**. You'll save this as a variable in CI in a later step. ### Trunk Token You can find your token under **Settings** → **Organization** → **General**, in the **API** section. Since this is a secret, do not leak it publicly. Ensure you get your *organization token*, not your project/repo token. ## Add the Trunk Token as a Secret Store the Trunk slug and API token obtained in the previous step as [Bamboo plan variables](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html). Name them `TRUNK_ORG_URL_SLUG` and `TRUNK_API_TOKEN` respectively, and mark `TRUNK_API_TOKEN` as a **Secret** variable in the Bamboo UI to prevent it from appearing in build logs. ## Upload to Trunk Add an `Upload Test Results` step after running tests in each of your Bamboo jobs that run tests. This should be minimally all jobs that run on pull requests, as well as from jobs that run on your [stable branches](../../detection#stable-branches), for example, `main`, `master`, or `develop`. It is important to upload test results from CI runs on [**stable branches**](../../detection#stable-branches), such as `main`, `master`, or `develop`. This will give you a stronger signal about the health of your code and tests. Trunk can also detect test flakes on PR and merge branches. To best detect flaky tests, it is recommended to upload test results from stable, PR, and merge branch CI runs. [Learn more about detection](../../detection) ### Example Bamboo Plan Spec The following is an example of a [Bamboo Plan Spec](https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html) that uploads test results after your tests run. The upload step is placed under `final-tasks` so it runs even when tests fail. Note: you must either run `trunk` from the repo root when uploading test results or pass a `--repo-root` argument. To find out how to produce the report files the uploader needs, see the instructions for your test framework in the [frameworks](../frameworks/) docs. ```yaml XML theme={null} version: 2 plan: project-key: key: name: Run Tests and Upload to Trunk.io Run Tests and Upload to Trunk: key: tasks: - checkout: description: Checkout Source Code - script: name: Run Tests body: | # Your test command here final-tasks: - script: name: Upload Test Results to Trunk.io body: | curl -fL --retry 3 "https://github.com/trunk-io/analytics-cli/releases/latest/download/trunk-analytics-cli-x86_64-unknown-linux.tar.gz" | tar -xz chmod +x trunk-analytics-cli ./trunk-analytics-cli upload \ --junit-paths "" \ --org-url-slug ${bamboo.TRUNK_ORG_URL_SLUG} \ --token ${bamboo.TRUNK_API_TOKEN} variables: TRUNK_ORG_URL_SLUG: TRUNK_API_TOKEN: ``` ```yaml Bazel theme={null} version: 2 plan: project-key: key: name: Run Tests and Upload to Trunk.io Run Tests and Upload to Trunk: key: tasks: - checkout: description: Checkout Source Code - script: name: Run Tests body: | # Your test command here final-tasks: - script: name: Upload Test Results to Trunk.io body: | curl -fL --retry 3 "https://github.com/trunk-io/analytics-cli/releases/latest/download/trunk-analytics-cli-x86_64-unknown-linux.tar.gz" | tar -xz chmod +x trunk-analytics-cli ./trunk-analytics-cli upload \ --bazel-bep-path \ --org-url-slug ${bamboo.TRUNK_ORG_URL_SLUG} \ --token ${bamboo.TRUNK_API_TOKEN} variables: TRUNK_ORG_URL_SLUG: TRUNK_API_TOKEN: ``` ```yaml XCode theme={null} version: 2 plan: project-key: key: name: Run Tests and Upload to Trunk.io Run Tests and Upload to Trunk: key: tasks: - checkout: description: Checkout Source Code - script: name: Run Tests body: | # Your test command here final-tasks: - script: name: Upload Test Results to Trunk.io body: | curl -fL --retry 3 "https://github.com/trunk-io/analytics-cli/releases/latest/download/trunk-analytics-cli-x86_64-unknown-linux.tar.gz" | tar -xz chmod +x trunk-analytics-cli ./trunk-analytics-cli upload \ --xcresult-path \ --org-url-slug ${bamboo.TRUNK_ORG_URL_SLUG} \ --token ${bamboo.TRUNK_API_TOKEN} variables: TRUNK_ORG_URL_SLUG: TRUNK_API_TOKEN: ``` ### Uploading from Pull Request Builds To detect flaky tests on pull requests, configure your plan to create [plan branches](https://confluence.atlassian.com/bamboo/using-plan-branches-289276872.html) for pull requests. Add the following to your Plan Spec: ```yaml theme={null} branches: create: for-pull-request: accept-fork: false ``` Bamboo automatically sets the `bamboo_repository_pr_key` variable on PR builds, which the Trunk Analytics CLI uses to associate uploads with the correct pull request. **PR number not detected?** If your Bamboo setup does not set `bamboo_repository_pr_key`, you can override it by passing the `--pr-number` flag or setting the `TRUNK_PR_NUMBER` environment variable when running the upload command. The examples above use the Linux x64 binary. If your CI runs on a different platform, see the [Trunk Analytics CLI](../../reference/cli-reference#manual-download) page for all available platform downloads. See the [uploader.md](../../reference/cli-reference.md) for all available command line arguments and usage. ### Stale files Ensure you report every test run in CI and **clean up stale files** produced by your test framework. If you're reusing test runners and using a glob like `**/junit.xml` to upload tests, stale files not cleaned up will be included in the current test run, throwing off detection of flakiness. You should clean up all your results files after every upload step. ## Validate Your Uploads Once your pipeline has run on a stable branch, head to [app.trunk.io](https://app.trunk.io) and confirm Trunk received your results. * The **Uploads** tab lists every report Trunk has ingested, with status and any warnings (missing file paths, malformed XML, and so on). * The **Tests** tab shows individual test cases once an upload has been processed. If a recent run isn't showing up, check your CI logs for upload errors and confirm your `TRUNK_API_TOKEN` and `TRUNK_ORG_URL_SLUG` secrets are set on the project running the pipeline.