Bazel
A guide for generating Trunk-compatible test reports with Bazel
Last updated
A guide for generating Trunk-compatible test reports with Bazel
Last updated
You can automatically 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.
By the end of this guide, you should achieve the following before proceeding to the to configure your CI provider.
After correctly generating reports following the above steps, you'll be ready to move on to the next steps to .
Trunk can parse JSON serialized 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:
You can specify the path of the generated report through the build_event_json_file option:
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.
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:
Configure your CI to upload test runs to Trunk. Find the guides for your CI framework below:
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 .
If your CI environment is set up to , you will need the following flag to pull the reports from the remote execution engine:
You can validate your test reports using the . If you don't have it installed already, you can install and run the validate command like this:
This will not upload anything to Trunk. To improve detection accuracy, you should address all errors and warnings before proceeding to the next steps.
