Bitbucket

Bitbucket is Atlassian's Git and Mercurial repository hosting service, offering code management, pull requests, code review, and CI/CD pipelines within the Atlassian ecosystem. Unlike GitHub's community focus or GitLab's all-in-one approach, Bitbucket emphasizes enterprise team collaboration through deep integration with Jira (issue tracking), Confluence (documentation), Trello (project management), and other Atlassian products. Teams using Atlassian suite get seamless workflows—link commits to Jira issues, trigger CI/CD from Jira boards, update tickets automatically on deployments. Bitbucket offers both cloud (Bitbucket Cloud) and self-hosted (Bitbucket Data Center) options, with Bitbucket Pipelines providing integrated CI/CD similar to GitHub Actions or GitLab CI. Enterprises choose Bitbucket for Atlassian ecosystem integration, unlimited private repositories on free tier, and enterprise features like IP allow listing and mandatory 2FA.

Best For:
Bitbucket excels for teams already using Atlassian products and enterprises requiring deep Jira integration. It's ideal for companies standardized on Atlassian ecosystem (Jira for project management, Confluence for docs), teams requiring Jira-Git integration (automatic issue status updates from commits, deployment visibility in Jira), enterprises needing advanced security (IP restrictions, required 2FA, audit logs), small teams wanting unlimited free private repositories (better than GitHub's limits), Mercurial users (Bitbucket supports both Git and Mercurial), and organizations requiring self-hosted Git with enterprise features (Bitbucket Data Center). Bitbucket is particularly valuable when Jira integration eliminates manual ticket updates, or when Atlassian licensing bundles make Bitbucket cost-effective versus separate Git hosting.

Common Questions

Bitbucket vs. GitHub vs. GitLab: how to choose?
Choose GitHub for open source, largest community, marketplace ecosystem, and best social features. Choose GitLab for complete DevOps platform (security, compliance), self-hosting, and all-in-one tooling. Choose Bitbucket when you use Jira/Confluence (Atlassian integration is unmatched), need enterprise security features, or want unlimited free private repos for small teams. Bitbucket is strongest within Atlassian ecosystem; outside that, GitHub or GitLab may offer better standalone value.

Does Bitbucket Pipelines compete with Jenkins/GitHub Actions?
Yes, Bitbucket Pipelines is built-in CI/CD running Docker containers to build, test, and deploy code. Define pipelines in bitbucket-pipelines.yml, get 50 build minutes/month free (up to 3,500 on paid plans). Simpler than Jenkins (no server to maintain), comparable to GitHub Actions and GitLab CI. However, pipeline minutes are more limited than competitors (GitHub: 2,000 free, GitLab: 400). Many teams use self-hosted runners or Jenkins alongside Bitbucket for unlimited builds.

Can I self-host Bitbucket?
Yes, Bitbucket Data Center is Atlassian's self-hosted enterprise Git solution. Unlike GitHub (no self-host) or GitLab (free self-host option), Bitbucket self-hosting requires Data Center license ($2,300+/year for 25 users). Data Center adds high availability, disaster recovery, and enterprise features. No free self-hosted option—Bitbucket Server (older product) has reached end-of-life, replaced by Data Center only.

What happened to Mercurial support?
Bitbucket Cloud has discontinued Mercurial support, forcing migration to Git. Bitbucket was one of the last major platforms supporting Mercurial. Existing Mercurial repos were frozen; teams had to migrate to Git repos or export elsewhere. This alienated some Mercurial users but aligned Bitbucket with industry (Git is now de facto standard).

Pricing & Plans

Bitbucket Cloud:

Free:

• Unlimited private repositories
• Up to 5 users
• 50 build minutes/month (Pipelines)
• 1 GB Git LFS storage
• Community support
  Good for small teams and personal projects.

Standard: $3/user/month (5+ users required, minimum $15/month)

• Everything in Free, plus:
• 2,500 build minutes/month
• 5 GB Git LFS storage
• Merge checks, deployment permissions
• Standard support

Premium: $6/user/month

• Everything in Standard, plus:
• 3,500 build minutes/month
• 10 GB Git LFS storage
• IP allow listing, required 2FA
• Deployment environments, audit logs
• Premium support, 99.9% SLA

Bitbucket Data Center (Self-Hosted):

• 25 users: $2,300/year
• 50 users: $5,200/year
• 100 users: $10,000/year
• 500+ users: Enterprise pricing

Includes high availability, disaster recovery, enterprise security, unlimited repos, unlimited build agents (self-hosted). Infrastructure costs additional (servers, database, storage).

Additional Costs:

• Extra build minutes (Cloud): $10 per 1,000 minutes
• Extra Git LFS storage: ~$5/GB/month
• Jira/Confluence bundled discounts available

Limitations

Bitbucket's free tier build minutes (50/month) are far lower than GitHub (2,000) or GitLab (400)—inadequate for active projects without self-hosted runners. Bitbucket's community is smaller than GitHub's—fewer public repos, less discovery, minimal social features. No free self-hosting option (unlike GitLab CE)—Data Center requires paid license, limiting appeal for startups wanting self-hosted Git. Bitbucket's UI is less modern than GitHub/GitLab—some developers find it clunky or slower. Bitbucket Pipelines has smaller ecosystem than GitHub Actions—fewer pre-built actions/integrations available. Mandatory 5-user minimum for paid plans (Standard/Premium) makes it expensive for 2-3 person teams. Bitbucket's focus on Atlassian ecosystem means standalone value (without Jira/Confluence) is lower—GitHub or GitLab are better for teams not using Atlassian products. Mercurial discontinuation alienated longtime users.

Getting Started

Bitbucket Cloud:

1. Sign up at bitbucket.org (free, up to 5 users)
2. Create workspace (organization) and repository
3. Clone: git clone https://username@bitbucket.org/workspace/repo.git
4. Push code normally with Git

Create CI/CD Pipeline:
Create bitbucket-pipelines.yml in repository root:

image: node:18

pipelines:
  default:
    - step:
        name: Build and Test
        caches:
          - node
        script:
          - npm install
          - npm test
          - npm run build
        artifacts:
          - dist/**
  branches:
    main:
      - step:
          name: Deploy to Production
          deployment: production
          script:
            - echo "Deploying to production..."

Push to Bitbucket—pipeline runs automatically. View: Pipelines tab in repo.

Link Jira Issues:
In commit messages or pull requests, reference Jira issues: git commit -m "PROJ-123 Fix bug in authentication". Bitbucket automatically links to Jira, updates issue with commit/deployment info. View commits and deployments in Jira issue panel.

Pull Requests:
Create branch, push changes, Bitbucket prompts for pull request. Add reviewers, link Jira issue, add description. Require approvals, run builds, merge when ready. Use merge checks (Premium) to enforce requirements (passing builds, approvals, Jira links).

Branch Permissions:
Repository settings → Branch permissions → Restrict who can push/merge to protected branches (e.g., main). Require pull requests, specify reviewers, prevent force pushes.

Self-Hosted Bitbucket Data Center:
Requires:

• License key (purchase from Atlassian)
• PostgreSQL database
• Shared file system (NFS)
• Load balancer (for high availability)

Install via:

# Download installer from Atlassian
wget https://www.atlassian.com/software/bitbucket/downloads/binary/atlassian-bitbucket-8.x.x-x64.bin

# Run installer
chmod +x atlassian-bitbucket-8.x.x-x64.bin
sudo ./atlassian-bitbucket-8.x.x-x64.bin

Follow installation wizard. Configure database, license, base URL. Access setup wizard at http://server:7990. For production, use Atlassian's recommended hardware specifications and deployment architectures.

Integrations:
Connect Bitbucket to:

• Jira: Automatic issue linking, deployment tracking, smart commits
• Confluence: Link documentation to repos, embed code snippets
• Trello: Attach commits to Trello cards
• Slack: Notifications for pushes, PRs, builds
• Jenkins: Trigger builds from Bitbucket webhooks
• AWS/Azure/GCP: Deploy using Bitbucket Pipelines integrations

Workspaces & Projects:
Workspaces contain Projects contain Repositories. Use Projects to group related repos (e.g., "Mobile Apps" project with iOS/Android repos). Set permissions at workspace, project, or repo level.

Follow Bitbucket documentation, Atlassian Community forums, and Bitbucket blog for guides and best practices. For Atlassian ecosystem integration, refer to Jira Software and Confluence documentation.