Skip to main content

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.

You can automatically detect and manage flaky tests in your Bazel projects by integrating with Trunk. This document explains how to configure Bazel to output compatible reports that can be uploaded to Trunk for analysis.

​
Setup steps

Work through the steps below in order. Once you’ve finished the last one, you’ll be ready to move on to configure uploads in CI.
1

Generate a compatible test report

2

Configure the report file path or glob

3

Disable retries for better detection accuracy

4

Test uploads locally

​
Generating Reports

Trunk can parse JSON serialized Build Event Protocol (BEP) files to detect flaky tests. You can run tests with Bazel in CI with the nobuild_event_json_file_path_conversion option to produce a serialized BEP file: 
bazel test <TARGETS> \
    --nobuild_event_json_file_path_conversion

​
Report File Path

You can specify the path of the generated report through the build_event_json_file option: 
bazel test <TARGETS> \
    --nobuild_event_json_file_path_conversion
    --build_event_json_file=build_events.json
Trunk can parse the build_events.json file to locate your test reports. You will still need to configure your test runners to output compatible reports, and you can refer to the guides for individual test frameworks.

​
Build Without the Bytes

If your CI environment is set up to build without the bytes, you will need the following flag to pull the reports from the remote execution engine: 
--remote_download_regex='.*/test.xml'

​
Disable Retries

You need to disable automatic retries if you previously enabled them for more accurate detection results. Disable retries if you’re retrying tests using the --flaky_test_attempts command line option or retrying in your test runner.

​
Try It Locally

​
The Validate Command

SKU="trunk-analytics-cli-x86_64-unknown-linux.tar.gz"
curl -fL --retry 3 \
  "https://github.com/trunk-io/analytics-cli/releases/latest/download/${SKU}" \
  | tar -xz

chmod +x trunk-analytics-cli
./trunk-analytics-cli validate --bazel-bep-path=build_events.json

​
Test Upload

Before modifying your CI jobs to automatically upload test results to Trunk, try uploading a single test run manually. You make an upload to Trunk using the following command: 
./trunk-analytics-cli upload --bazel-bep-path=build_events.json \
    --org-url-slug <TRUNK_ORG_SLUG> \
    --token <TRUNK_ORG_TOKEN>

​
Next Steps

Configure your CI to upload test runs to Trunk. Find the guides for your CI framework below:
azure

Azure DevOps Pipelines

bitbucket

BitBucket Pipelines

buildkite

BuildKite

circle-ci

CircleCI

drone

Drone CI

github

GitHub Actions

gitlab

GitLab

jenkins

Jenkins

semaphore

Semaphore

teamcity

TeamCity

travis

Travis CI

other

Other CI Providers