Bitbucket
An integrated continuous integration and delivery service built natively into Bitbucket Cloud, providing seamless Atlassian ecosystem automation.
About Bitbucket
Bitbucket Pipelines is the native CI/CD capability integrated directly into Bitbucket Cloud. Designed by Atlassian, it completely removes the need to configure, manage, and synchronize a separate CI server. The service executes builds in ephemeral Docker containers, driven by a simple bitbucket-pipelines.yml file located in the root of the repository, enabling a true pipeline-as-code workflow.
The defining strength of Pipelines is its seamless integration with the broader Atlassian toolchain. It provides native, zero-configuration visibility into Jira Software, automatically updating issue statuses based on build deployments, and can push release notifications directly to Confluence or Opsgenie. This interconnectedness allows project managers and developers to track the lifecycle of a feature from a Jira ticket all the way to production deployment without leaving their primary workspace.
Bitbucket Pipelines pools build minutes at the workspace level, simplifying billing for teams working across multiple microservices. In addition to Atlassian-managed cloud runners, the platform supports self-hosted runners, allowing teams to execute specialized workloads or build iOS applications on their own macOS hardware without consuming their cloud build minute allowance.
Key Features
- Native Atlassian Integration: Automatically update Jira issues, track deployment environments, and notify Opsgenie based on pipeline success or failure.
- Docker-Based Execution: Run builds inside isolated Docker containers, allowing developers to define exact environments and dependencies for reproducible builds.
- Workspace Minute Pooling: Share a single pool of build minutes across all repositories and users within an organizational workspace, eliminating per-repo limits.
- Self-Hosted Runners: Execute builds on your own Linux, Windows, or macOS infrastructure to access internal networks or avoid consuming cloud build minutes.
- Deployments Dashboard: Track which code versions are running in specific environments (Test, Staging, Production) directly within the Bitbucket interface.
- OpenID Connect (OIDC): Securely authenticate with cloud providers like AWS or GCP without needing to store long-lived secret keys in the platform.
Pricing
-
Free Plan: $0/month Includes up to 5 users and a pooled 50 build minutes per month.
-
Standard Plan: $3.65/user/month Includes a pooled 2,500 build minutes per month. Extra minutes can be purchased in packs of 1,000 for $10.
-
Premium Plan: $7.25/user/month Includes a pooled 3,500 build minutes per month, advanced deployment permissions, enforced merge checks, and IP allowlisting.
Use Cases
- Syncing CI/CD deployment statuses automatically to Jira issues to keep product managers informed without manual updates.
- Deploying infrastructure-as-code securely to AWS using short-lived OIDC tokens rather than static IAM credentials.
- Standardizing microservice deployments using Bitbucket Pipes, utilizing pre-built actions to push images to Docker Hub or deploy to Kubernetes.
- Utilizing a self-hosted macOS runner to automate Apple App Store releases for a mobile development team without leaving Bitbucket.
Pros & Cons
Pros:
- Zero friction for teams already using Bitbucket; CI/CD is available immediately without third-party integrations.
- The synergy with Jira provides unparalleled visibility for project management and DevOps tracking.
- The workspace-level pooling of build minutes makes cost management predictable across multiple repositories.
Cons:
- Falls short on advanced CI features (like matrix build visualizations or complex DAGs) compared to specialized tools like GitHub Actions or GitLab CI.
- The free tier allowance of 50 minutes is exceptionally low and only suitable for trivial hobby projects.
Integrations
Jira, Confluence, Opsgenie, AWS, Google Cloud, Microsoft Azure, Slack, Docker, Snyk
FAQ
Do I need to install a separate server for Bitbucket Pipelines?
No, Bitbucket Pipelines is a fully managed cloud service built directly into Bitbucket Cloud. You only need to add a YAML configuration file to your repository to start running builds.
How are build minutes calculated?
Build minutes are pooled at the workspace level, meaning all users and repositories share a single monthly allowance based on your plan (e.g., 2,500 minutes on Standard). You do not pay per individual repository.
Can I use Bitbucket Pipelines for iOS development?
Yes, but because Atlassian does not provide managed macOS runners, you must utilize the 'Self-Hosted Runner' feature to connect your own Mac hardware to Bitbucket to execute the iOS builds.
What are Bitbucket Pipes?
Pipes are reusable snippets of code that make it easy to configure powerful CI/CD tasks (like deploying to AWS, sending a Slack message, or scanning with SonarQube) by just adding a few lines to your YAML file.
How does OIDC integration improve security?
OpenID Connect (OIDC) allows your pipeline to request short-lived, temporary access tokens from cloud providers (AWS, GCP) during the build. This eliminates the massive security risk of storing permanent, hard-coded API keys in your repository secrets.
Tags:
Last edited
October 30, 2026 at 10:49 AM by Venkatraman Chandrasekaran
