Github Action enabling integration between Junit runners and Trunk Analytics.

Usage

Running this action will upload junit.xml files to Trunk Flaky Tests.

Example

name: Upload Test Results to Trunk
on:
  workflow_dispatch:

jobs:
  upload-test-results:
    runs-on: ubuntu-latest
    name: Run tests and upload results
    timeout-minutes: 60
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Run tests
        # Execute your tests.
        run: mkdir -p target/path && touch target/path/junit_report.xml

      - name: Upload results
        if: "!cancelled()"
        uses: trunk-io/analytics-uploader@main
        with:
          # Path to your test results.
          junit-paths: target/path/**/*_test.xml
          # Provide your Trunk organization url slug.
          # To find your org slug, log into app.trunk.io and you should be redirected to a URL like:
          # https://app.trunk.io/my-trunk-org-slug/repo-owner/repo-name/ci-analytics
          org-slug: my-trunk-org-slug
          # Provide your Trunk API token as a GitHub secret.
          # You can find Trunk token by navigating to app.trunk.io → Settings → Manage Organization → Organization API Token → View.
          # To add it as a GitHub secret, see https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions.
          token: ${{ secrets.TRUNK_API_TOKEN }}
        continue-on-error: true

Inputs

Parameter	Description
junit-paths	Required. Comma-separated list of glob paths to junit files.
org-slug	Required. Organization slug.
token	Optional. Organization token. Defaults to TRUNK_API_TOKEN env var.
repo-head-branch	Optional. Branch of repository head.
repo-root	Optional. Root directory of the repository.
team	Optional. Team that owns the upload.
run	Optional. Command to run before uploading test results.
cli-version	Optional. Version of the uploader to use.

Questions

For any questions, contact us on Slack or refer to our docs.