Delivering to Bitbucket

Integrate your pipelines with BitBucket repositories.

If you would like to fully integrate Supernova with your organization's Bitbucket account, you can grant Supernova access to any Bitbucket repository to create pull requests on your behalf.

If you prefer not to authorize access to a repository that contains production code, it is also possible to create a separate repository for Supernova-created data (to be used as a git submodule). This method eliminates any possibility for Supernova to access parts of the code not maintained by Supernova.

With the secure Bitbucket authentication, Supernova will have the following permissions:

  • Read access to metadata
  • Read and write access to code and pull requests

Authorize Bitbucket

To authorize Bitbucket from the Account → Workspace settings page:

  1. Select the Integrations tab.
  2. Under Bitbucket, click Connect to sign in to your Bitbucket account.
  3. You can then authorize via OAuth or a personal access token.

To authorize Bitbucket from the New pipeline dialog:

  1. Choose Open Bitbucket pull request as the delivery method.
  2. Click Connect Bitbucket to sign in to your Bitbucket account. You can then authorize via OAuth or a personal access token.

After your Bitbucket authorization is complete, you will now see a list of repositories and branches to choose from during hook or build configuration.

Revoke Bitbucket authorization

To revoke your Bitbucket authorization at any time:

  1. Go to your Workspace settings, located in the top right corner.
  2. Select the Integrations tab.
  3. Under the Bitbucket section, click Remove connection.

Choosing a repository and relative path

The repository you selected is where the code from a pipeline will be exported. You can also specify a relative path to export to for each pipeline separately.

The path entered is relative to the repository root, for example, lib/design-system/assets.