Integrate App percy with Probo.CI

Integrate App percy with Probo.CI, a CI service that builds preview environments for every pull request

Follow these steps to integrate App percy with Probo.CI:

Configuring Probo.CI environment variables

Start by configuring PERCY_TOKEN, our project-specific, write-only API token. It can be found in your App percy project settings.

In your Probo.CI project configuration (.probo.yaml), expose PERCY_TOKEN via the secrets field, or set it through the Probo.CI dashboard so the value is hidden in build logs.

Alternatively, you can export the variable as part of your build script:

Commit, branch, and pull request information

App percy auto-detects Probo.CI builds when the PROBO_ENVIRONMENT environment variable is set to TRUE. Probo.CI exposes:

• COMMIT_REF — commit SHA
• BRANCH_NAME — branch name
• PULL_REQUEST_LINK — pull request URL (the trailing path segment is used as the PR number)

If any of these variables are unavailable, you can fall back to PERCY_COMMIT, PERCY_BRANCH, or PERCY_PULL_REQUEST to populate the corresponding fields manually. See the environment variables docs page for more details.

Run your tests

With your environment configured, run your App percy snapshots via your test suite or another mechanism. Your App percy build will be created with the correct meta-data.

Parallelized build processes

If you parallelize your build across multiple jobs, set PERCY_PARALLEL_TOTAL to the total number of parallel runs. App percy automatically uses Probo.CI’s BUILD_ID as the parallel build nonce. See Parallel test suites for more details.

Reference Topic

• Webhook Payloads