Bitbucket Cloud Integration
What does the Bitbucket integration do?
Bitbucket Cloud connects with either a workspace or project access token, or an Atlassian account email plus API token. zop.dev lists repositories and branches through the Bitbucket Cloud REST API and uses the connection to clone code for builds and deployments.
Coverage by category
Teams on Bitbucket Cloud connect with either a workspace/project access token or an Atlassian account email plus API token. zop.dev lists your repositories and branches and uses the connection to clone code for builds and deployments.
Two credential shapes against the Bitbucket REST API
Talks directly to the Bitbucket Cloud REST API. Two credential shapes are accepted: a token used as a bearer credential, or username-plus-password style (Atlassian email and API token). The connection is validated before saving.
Make a token, paste it, deploy from a branch
- Create a Bitbucket access token (workspace or project scoped) or an Atlassian API token.
- Settings > Integrations > Bitbucket; paste credentials.
- Repositories and branches appear in the deploy flow.
Listing repositories and branches, plus clone access
Repository and branch listing, clone access for builds.
Which credential shape to use
A workspace or project access token is scoped to the workspace and outlives any individual, which makes it the better long-term choice. The email-plus-API-token pair authenticates as a person and carries that person’s full Bitbucket reach.
Bitbucket Cloud only
Bitbucket Data Center and Server are not supported. If you self-host Bitbucket, the connection will not authenticate. That is a hosting limitation rather than a configuration problem, and it is worth knowing before you start rather than after.
Branches drive deploys
Once connected, zop.dev lists branches per repository so a deployment can track one: push to it and the service redeploys. Point staging at a long-lived branch and production at your release branch rather than wiring both to the same one.
Limits worth knowing before you connect
Bitbucket Cloud only — Bitbucket Data Center / Server is not supported.
Bitbucket integration: common questions
Does this work with Bitbucket Data Center or Server?
No. Bitbucket Cloud only. A self-hosted Bitbucket will not authenticate, and that is a hosting limitation rather than something to configure around.
Which Bitbucket credential should I use?
A workspace or project access token. It is scoped to the workspace and outlives any individual. The Atlassian email plus API token pair authenticates as a person and carries that person's full Bitbucket reach, which is more access than a build integration needs.
Can a deployment track a specific Bitbucket branch?
Yes. Branches are listed per repository, and a deployment that tracks one redeploys when you push to it. Point staging at a long-lived branch and production at your release branch rather than wiring both to the same one.
No active rule family targets Bitbucket Cloud Integration today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.