Table of Contents
Table of Contents
Further Reading
What Does Bitbucket Mean?
Bitbucket is a Git hosting service developed by Atlassian. Teams use it to host repositories, manage pull requests, review code, and automate CI/CD pipelines.
Bitbucket is closely tied to the Atlassian ecosystem. It integrates directly with Jira, Confluence, and Trello to support agile project management.
Bitbucket vs. GitHub vs. GitLab
Why Bitbucket Matters
Development teams adopt Bitbucket for:
- Secure hosting for source code repositories
- Code review through pull request workflows
- Jira integration for issue tracking and agile boards
- Bitbucket Pipelines for continuous integration and delivery
- Fine-grained permissions for repositories and branches
For organizations on Atlassian products, Bitbucket connects planning, code, and deployment in one workflow.
Common Use Cases
- Repository hosting: private or public Git repositories
- Pull request collaboration: inline comments and approvals
- Pipeline automation: builds, tests, and deployments with Bitbucket Pipelines
- Issue linking: commits and branches tied to Jira issues
- Compliance controls: branch permissions and merge checks
How Bitbucket Works with Testkube
Testkube connects to Bitbucket repositories that hold test definitions, workflows, and configuration files. Teams can:
- Version tests with code: store test workflows next to the application
- Trigger on events: run tests on commits, pull requests, or pipeline steps
- Keep one source of truth: application code and test logic live together
- Collaborate in place: review test changes in normal pull requests
Testing follows the same GitOps practices teams already use in Bitbucket.
Real-World Example
A B2B SaaS team uses Jira, Confluence, and Bitbucket. Their Bitbucket Pipelines ran heavy integration tests on shared runners, which slowed every pull request.
- Store workflows: Testkube workflow definitions live in the Bitbucket repo.
- Trigger from Pipelines: a pipeline step starts the Testkube run.
- Run in Kubernetes: tests execute in the staging cluster, close to the services.
- Link results: pull requests show pass or fail, tied to the Jira issue.
Best Practices for Testing with Bitbucket
- Keep tests in the same repo: code and tests change together.
- Require passing checks: use merge checks to block failing pull requests.
- Offload heavy suites: run long tests in Kubernetes instead of pipeline runners.
- Use repository variables: store tokens securely, never in YAML.
- Link to Jira: connect test failures to the issues they affect.



