CI Configuration (non-GitHub)

You'll need

• Getting Started complete
• your repository is built on a CI provider other than GitHub Actions (GitLab CI, CircleCI, Jenkins, Azure Pipelines, Buildkite, etc.)

You'll have

• CI uploading reports to Flakiness.io at the end of each test run.

On GitHub Actions?

If your repo uses GitHub Actions, read GitHub Actions Setup instead — it uses OIDC and doesn’t need an access token.

How it works

All Flakiness.io reporters upload reports automatically when the FLAKINESS_ACCESS_TOKEN environment variable is set. This works with any CI provider — Jenkins, GitLab CI, CircleCI, Azure Pipelines, Buildkite, and others.

Setup

1. Get your project’s access token from the Flakiness.io project settings.
2. Add it as a secret environment variable named FLAKINESS_ACCESS_TOKEN in your CI provider’s settings.
3. Make sure the variable is exposed to the step that runs your tests.

The reporter detects the token and uploads results at the end of every test run.

Example

# Generic CI script
export FLAKINESS_ACCESS_TOKEN="$YOUR_CI_SECRET"

# Run tests with your framework of choice
npx playwright test    # or pytest, or: flakiness upload ./flakiness-report

Reporter configuration

Refer to your test runner’s documentation for configuration details specific to each reporter.