BitBucket

1. What you get with BitBucket
2. How the integration works
3. Good to know

Bitbucket is Atlassian's Git hosting, and its real strength is the ecosystem around it: deep Jira integration, Trello links and the workflow glue teams on Atlassian tooling already rely on. Commits reference issues, branches spawn from tickets — and with Rocketeers connected, pushes become deployments. Your code, your project management and your servers finally speak the same language.

#What you get with BitBucket

• Automatic deployments on every push to the branch you choose.
• Private repositories and existing branch strategies supported out of the box.
• Jira issue keys in your commits keep linking through — deployment doesn't interrupt the Atlassian workflow.
• Deploy different branches to different environments without touching your repo settings.
• No custom deploy scripts or pipelines needed just to get code onto a server.

#How the integration works

Authorise Rocketeers with your Bitbucket account, select the workspace and repository for each site, and pick the deployment branch. Rocketeers adds a webhook to the repository so Bitbucket announces every push; pushes to the watched branch trigger a deployment, everything else is ignored. Access can be revoked at any time from your Bitbucket settings, and Rocketeers only touches the repositories you connect.

#Good to know

• Works with both personal accounts and team workspaces; workspace admins control which integrations are allowed.
• Bitbucket's free plan supports private repositories for small teams, so there's no paid requirement to deploy privately.
• If you already run Bitbucket Pipelines for CI, keep it — Rocketeers deploys on push and doesn't conflict with your build pipeline.
• Bitbucket applies soft repository size limits from around 1 GB — worth watching for media-heavy repos. Keep large binaries out of Git and let your storage provider handle them instead.