Percy Developer Hub

Welcome to the Percy Developer Hub. You'll find comprehensive guides and documentation to help you start working with Percy as quickly as possible, as well as support if you get stuck. Let's jump right in!

Bitbucket Pipelines

­čĹŹ

Covered in this doc

Integrating Percy with your Bitbucket Pipelines environment

Configuring environment variables


Start by configuring PERCY_TOKEN, our project-specific, write-only API token. It can be found in your Percy project settings and set via your Bitbucket Pipelines settings.

Bitbucket Pipelines provide a variety of ways to configure environment variables. Because each Percy project is usually associated with just one repository, we recommend setting PERCY_TOKEN up as a repository variable, and making it secure.

In your Bitbucket project go to Settings > Pipelines > Respository Variables.

Then set PERCY_TOKEN to the write-only token from your Percy project. The token value can be found in each Percy project's settings.

Bitbucket Pipelines' Repository variable settings

­čôś

Keep your Percy token secret

Anyone with access to your token can add builds to your project, though they cannot read data.

For Bitbucket Pipelines, make sure the "Secure" checkbox is checked.

With the addition of the PERCY_TOKEN repository variable, any snapshots you take in this pipeline will be sent to the associated Percy project. Percy will automatically detect the commit SHA, branch name, and pull request number from the Pipelines environment.

Updated about a year ago

Bitbucket Pipelines


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.