Vercel for Bitbucket

Vercel for Bitbucket automatically deploys your Bitbucket projects with Vercel, providing Preview Deployment URLs, and automatic Custom Domain updates.

Commits pushed to Bitbucket are automatically built and deployed with Vercel.

Deploying a Bitbucket Repository

Learn how to create a new Vercel Project from a Bitbucket repository and enable automatic deployments on every branch push here.

Changing the Bitbucket Repository of a Project

If you'd like to connect your Vercel Project to a different Bitbucket repository or disconnect it, you can do so from the Git section in the Project Settings.

Default Behaviour

A Deployment for Each Push

Vercel for Bitbucket will deploy each push by default. This includes pushes and pull requests made to branches. This allows those working within the project to preview the changes made before they are pushed to production.

With each new push, if Vercel is already building a previous commit, the current build will be canceled to build the most recent commit so that you always have the latest changes deployed as quickly as possible.

Updating the Production Domain

If Custom Domains are set from a project domains dashboard, pushes and merges to the Production Branch (commonly "main") will be made live to those domains with the latest deployment made with a push.

If you decide to revert a commit that has already been deployed to production, the previous Production Deployment from a commit will automatically be made available at the Custom Domain instantly; providing you with instant rollbacks.

Preview URLs for Each Pull Request

The latest push to any pull request will automatically be made available at a unique preview URL based on the project name, branch, and team or username. These URLs will be given through a comment on each pull request.

A preview URL created from a pull request.

System Environment Variables

You may want to use different workflows and APIs based on Git information. To support this, the following System Environment Variables are exposed to your Deployments:

Name	Description
`VERCEL_GIT_PROVIDER`	The Git Provider the deployment is triggered from. In the case of Bitbucket, the value is always `bitbucket`.
`VERCEL_GIT_REPO_SLUG`	The slug of the Bitbucket repository that was deployed. Example: `my-site`.
`VERCEL_GIT_REPO_OWNER`	The Bitbucket user or team that the project belongs to. Example: `acme`.
`VERCEL_GIT_REPO_ID`	The ID of the Bitbucket repository the deployment is triggered from. Example: `{9e072df2-521e-4409-a01c-c984569fea20}`.
`VERCEL_GIT_COMMIT_REF`	The Bitbucket branch that the deployment was triggered by. Example: `improve-about-page`.
`VERCEL_GIT_COMMIT_SHA`	The Bitbucket sha of the commit the deployment was triggered by. Example: `fa1eade47b73733d6312d5abfad33ce9e4068081`.
`VERCEL_GIT_COMMIT_MESSAGE`	The message accompanying the Bitbucket commit that was deployed. Example: `Add John Doe to about page`.
`VERCEL_GIT_COMMIT_AUTHOR_LOGIN`	The name of the commit author on Bitbucket. Example: `John Doe`.
`VERCEL_GIT_COMMIT_AUTHOR_NAME`	Bitbucket profile URL of the commit author. Example: `https://bitbucket.org/%7B45585b19-b616-401e-89d3-1a47fddb7033%7D/`.

Missing Git Repository

When importing or connecting a Bitbucket repository, we require that you have Admin access to the corresponding repository, so that we can configure a webhook and automatically deploy pushed commits.

If a repository is missing when you try to import or connect it, make sure that you have Admin access configured for the repository.