diff --git a/flaky-tests/ci-providers/buildkite-quickstart.md b/flaky-tests/ci-providers/buildkite-quickstart.md index d3351c8..40672d0 100644 --- a/flaky-tests/ci-providers/buildkite-quickstart.md +++ b/flaky-tests/ci-providers/buildkite-quickstart.md @@ -6,7 +6,7 @@ description: Configure Buildkite jobs to upload test results to Trunk Flaky Test ### Introduction -Trunk Flaky Tests integrates with your CI by adding an `Upload Test Results` step in each of your testing CI jobs via the [Trunk Uploader CLI](../uploader.md). Just specify file path globs for JUnit XML files, supported by virtually all test frameworks. See the [Test Frameworks](../frameworks/) docs for instructions on producing JUnit XML output for your test runner. +Trunk Flaky Tests integrates with your CI by adding an `Upload Test Results` step in each of your testing CI jobs via the [Trunk Uploader CLI](../uploader.md). See the [Test Frameworks](../frameworks/) docs for instructions on producing JUnit XML output for your test runner, supported by virtually all test frameworks, which is what Trunk ingests. ### Step 1: Store a TRUNK\_TOKEN secret in your CI system @@ -14,25 +14,25 @@ In [app.trunk.io](http://app.trunk.io), navigate to: **`Settings` -> `Manage Organization` -> `Organization API Token`** -Store your API Token in a CI [secret](https://buildkite.com/docs/pipelines/secrets) named `TRUNK_TOKEN`. +Store your API Token in a [CI secret](https://buildkite.com/docs/pipelines/security/secrets/managing) named `TRUNK_TOKEN`. -### Step 2: Modify Buildkite test jobs to upload results to Trunk - -Add an `Upload Test Results` step after running tests in each of your CI jobs that run tests. This should be minimally all jobs that runs on pull requests, as well as from jobs that run on your main or protected branches (`main`, `master`, `develop`, etc) . - -#### Get your Organization Slug +### Step 2: Grab your Organization Slug To upload test results to Trunk, you'll need to pass a Trunk Org Slug to the upload command. Replace `TRUNK_ORG_SLUG` in the example workflow below with your actual Trunk Organization Slug, which you can find in: **`Settings` -> `Manage` -> `Organization` -> `Organization Slug`** -Your Trunk Organization Slug can just be pasted directly into your CI workflow, it's not a secret. +Your Trunk Organization Slug can just be pasted directly into your CI workflow; it's not a secret. + +### Step 3: Modify Buildkite jobs to upload test results + +Add an `Upload Test Results` 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 main or protected branches (`main`, `master`, `develop`, etc) . #### Example Buildkite Workflow -The following is an example of a buildkite workflow step to upload test results after your tests run. You must either run `trunk` from the repo root when uploading test results, or supply a `--repo-root` argument. +The following is an example of a buildkite 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 product the JUnit XML files the uploader needs, see instructions for your test framework in the [frameworks](../frameworks/ "mention") docs. +To find out how to produce the JUnit XML files the uploader needs, see the instructions for your test framework in the [frameworks](../frameworks/ "mention") docs. ```yaml steps: @@ -53,4 +53,4 @@ See the [uploader.md](../uploader.md "mention") for all available command line a #### Need Help? -Join the [Trunk Slack Community](https://slack.trunk.io) for live help and support. +Join the [Trunk Slack Community](https://slack.trunk.io) for live support. diff --git a/flaky-tests/ci-providers/readme.md b/flaky-tests/ci-providers/readme.md index f081f3a..a490efa 100644 --- a/flaky-tests/ci-providers/readme.md +++ b/flaky-tests/ci-providers/readme.md @@ -1,12 +1,11 @@ --- -description: >- - You can easily integrate Flaky Tests from any CI Provider. Please find - quickstart instructions below that match your setup. +description: You can easily integrate Flaky Tests from any CI Provider. --- # CI Providers -### Quickstart +Trunk Flaky Tests integrates with your CI by adding an `Upload Test Results` step in each of your testing CI jobs via the [Trunk Uploader CLI](../uploader.md). See the [Test Frameworks](../frameworks/) docs for instructions on producing JUnit XML output for your test runner, supported by virtually all test frameworks, which is what Trunk ingests. -
GitHub Actionsgithub-actions-quickstart.mdGitHub (1).png
BuildKitebuildkite-quickstart.mdBuildKite (1).png
CircleCIcircleci-quickstart.mdCircleCI.png
Drone CIdroneci.mddroneci.png
Gitlabgitlab.mdgitlab-logo.png
Jenkinsother-ci-providers-quickstart.mdjenkins-padded.png
Semaphoresemaphore-ci-quickstart.mdsemaphore-logo.png
Travis CItravisci.mdtravis-ci-logo.png
+### Quickstart +
GitHub Actionsgithub-actions-quickstart.mdgithub.png
BuildKitebuildkite-quickstart.mdbuildkite.png
CircleCIcircleci-quickstart.mdcircle-ci.png
Drone CIdroneci.mddrone.png
Gitlabgitlab.mdgitlab.png
Jenkinsother-ci-providers-quickstart.mdjenkins.png
Semaphoresemaphore-ci-quickstart.mdsemaphore.png
Travis CItravisci.mdtravis.png