Azure DevOps Pipelines

Trunk Flaky Tests integrates with your CI by adding a step in your Azure DevOps Pipelines to upload tests with the Trunk Uploader CLI.

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 to get started.

Before you start on these steps, see the Test Frameworks docs for instructions on producing a Trunk-compatible output for your test framework.

By the end of this guide, you should achieve the following.

• 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

After completing these checklist items, you'll be integrated with Trunk.

Add the Trunk Token as a Secret

Store the Trunk slug and API token obtained in the previous step in your Azure DevOps Pipelines as new variables named TRUNK_ORG_SLUG and TRUNK_TOKEN respectively.

Upload to Trunk

Add an upload 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 stable branches, for example, main, master, or develop.

You must upload tests from both PR and stable branchs, such as main, master, or develop in CI for Trunk to detect flaky tests. Trunk will not detect flaky tests without uploads from both PR and stable branches.

Learn more about detection

Add Uploader to Testing Pipelines

The following is an example of a workflow step to upload test results after your tests run. 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 Test Frameworks docs.

XML

trigger:
- main

pool:
  vmImage: ubuntu-latest

steps:
# ... Omitted steps

- script: |
    curl -fsSLO --retry 3 https://trunk.io/releases/trunk
    chmod +x ./trunk
    ./trunk flakytests upload --junit-paths "<XML_GLOB_PATH>" \
    --org-url-slug $(TRUNK_ORG_SLUG) \
    --token $(TRUNK_TOKEN)
  condition: always() # this should always run
  displayName: Upload test results to Trunk.io

Bazel

trigger:
- main

pool:
  vmImage: ubuntu-latest

steps:
# ... Omitted steps

- script: |
    curl -fsSLO --retry 3 https://trunk.io/releases/trunk
    chmod +x ./trunk
    ./trunk flakytests upload --bazel-bep-path <BEP_JSON_PATH> \
    --org-url-slug $(TRUNK_ORG_SLUG) \
    --token $(TRUNK_TOKEN)
  condition: always() # this should always run
  displayName: Upload test results to Trunk.io

XCode

trigger:
- main

pool:
  vmImage: ubuntu-latest

steps:
# ... Omitted steps

- script: |
    curl -fsSLO --retry 3 https://trunk.io/releases/trunk
    chmod +x ./trunk
    ./trunk flakytests upload --xcresults-path <XCRESULT_PATH> \
    --org-url-slug $(TRUNK_ORG_SLUG) \
    --token $(TRUNK_TOKEN)
  condition: always() # this should always run
  displayName: Upload test results to Trunk.io

See the Uploader CLI Reference 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.

Learn more about cleaning up artifacts in Azure DevOps Pipelines