Deployment Orchestration and Health Monitoring

1 post · Jun 2021 – Aug 2026

What this trail covers

Bitbucket Cloud is evolving its Deployments functionality into a more modular system. This includes introducing Concurrency Groups for managing step execution order and Environments for decoupling environment-specific variables, permissions, and branch restrictions from the full Deployments framework. These features aim to provide greater flexibility and control over CI/CD workflows, allowing users to leverage specific components without being forced into the entire Deployments structure. Dynamic Pipelines extend this by allowing serverless functions to alter pipeline configurations in real-time, enabling advanced organizational CI/CD orchestration and custom workflow logic.

All Atlassian trails

Aug 2026Introducing the redesigned deployments experienceThis post introduces a redesigned Deployments page for Bitbucket Pipelines. The redesign focuses on improving the user interface and experience for visualizing deployment status and history. Key changes include a column-based layout for environments (Test, Staging, Production), richer deployment cards displaying status, build number, commit hash, author, and time, and easily accessible deployment history panels. The page now supports live updates as pipelines run. Filtering capabilities have been enhanced to allow users to narrow results by author, environment name, and status. The post also includes a sample `bitbucket-pipelines.yml` configuration for triggering production deployments.
Jul 2026Custom deployment permissions for your environments (Beta)Introduces custom deployment permissions for Bitbucket Pipelines environments, allowing repository admins to define specific users and groups authorized to trigger deployments. This feature gates access to environments, preventing unauthorized deployments and supporting compliance workflows by separating code merge permissions from deployment permissions. It also details the UI for managing these permissions and known limitations.
Jun 2026Track Deployment status for your PRs (Beta)Introduces the Beta version of Deployment Status Tracking for pull requests, which surfaces live deployment statuses directly within the PR list view. This feature maps deployment status to the exact commit executed, providing immediate visibility into where code lives across environments. It eliminates manual tracking by displaying a dedicated Deployment column on the PR list view, showing environments (dev, staging, production) to which the latest PR commit has been deployed. Clicking a status badge displays a breakdown of up to 10 environments, with critical states (Failed, Stopped, In Progress, Successful) bubbling to the top. Dynamic environment renaming is supported. Technical constraints include tracking status only for the head commit of a PR, displaying statuses for deployments within the last 6 months, and a maximum of 10 environments per status.
Mar 2026OpenTelemetry traces for Bitbucket Pipelines via webhooksThis post introduces the exposure of Bitbucket Pipelines execution as OpenTelemetry (OTel) traces via webhook events. It details the span model (pipeline run, step, command, container attributes) and how to consume these traces in observability stacks like Grafana, Datadog, and Honeycomb. The goal is to provide end-to-end visibility, structured spans, resource metrics, and a standard format for correlating pipeline activity with application traces and incidents, aiding in performance bottleneck identification, reliability analysis, and capacity planning.
Dec 2025Pull request intervention for infrastructure-as-code risks with Bitbucket custom merge checksThis post introduces Bitbucket custom merge checks as a mechanism to intervene on "Known Risks" in infrastructure-as-code changes. It details how these checks can inspect pull requests for specific files (e.g., service descriptors), evaluate changes for known high-impact, difficult-to-rollback configurations, and report results to users. The implementation leverages the Forge ecosystem and the Bitbucket Cloud REST API to provide feedback and potentially fail merge checks, thereby mitigating the likelihood of severe incidents related to infrastructure changes.
Advertisement
Nov 2025How Bitbucket powers compliance and code quality at scaleThis post details enhancements to Bitbucket Cloud's security, compliance, and CI/CD capabilities. It highlights the platform's built-in security features (encryption, IP allowlisting, 2FA, SSO, audit logs) and its multi-region, sharded infrastructure for reliability and future data residency. Dynamic Pipelines are presented as a key feature for balancing compliance and developer autonomy in CI/CD, enabling runtime modifications for security scans, approved Docker images, self-hosted runners, selective test execution, and cost attribution. Customizable merge checks, including support for signed commits (GPG/SSH), are emphasized for enforcing code quality and compliance. The integration with Jira Service Management for automated change requests, approvals, and end-to-end traceability is also detailed. Future plans include hybrid licenses for Bitbucket Data Center and data residency options for Bitbucket Cloud.
Jun 2025Evolving deployments in Bitbucket Pipelines: Concurrency Groups and EnvironmentsIntroduces Concurrency Groups to manage step execution order in Bitbucket Pipelines, ensuring steps in the same group run one at a time in a FIFO manner, replacing restrictive deployment locks. Also introduces Environments, which decouple environment variables, admin permissions checks, and branch restrictions from the full Deployments framework, allowing for reuse across parallel steps. The post details example configurations and UI representation for Concurrency Groups, and notes that for deployment tracking, the `deployment` keyword is still required alongside `concurrency-group`.
Jun 2025New IP addresses for Bitbucket PipelinesThis post announces updates to the IP addresses used by Bitbucket Pipelines build environments. It requires users who employ firewalls, access lists, or security groups to restrict outgoing access to specific IP addresses to update their IP lists to allow connections to the new address list. A link to the updated IP list is provided.
Mar 2025Introducing the “retry” step failure strategy for Bitbucket PipelinesIntroduces the `retry` failure strategy for Bitbucket Pipelines, allowing automatic retries of failed steps up to a configurable `maxRetryCount`. This strategy can be applied to individual steps, parallel groups, and stages, with inheritance and overwriting capabilities. It also notes limitations such as incompatibility with deployment steps/stages and `fail-fast`, and that failure strategies are not additive. The post visually communicates retries in the Pipelines view and highlights the consumption of additional build minutes.
Mar 2025Easily share data between steps in Bitbucket PipelinesThis post introduces a new capability in Bitbucket Pipelines for sharing environment variables between steps within the same pipeline. Previously, this required workarounds like saving variables to artifact files. The new feature uses the `$BITBUCKET_PIPELINES_VARIABLES_PATH` and an `output-variables` field in the pipeline YAML to export variables. It details a 'last write wins' strategy for variable naming, security considerations (not for secrets), limits (50 variables, 100kb total size), and scope (pipeline lifetime). It also mentions that this functionality will be the basis for future features like conditional step execution.
Feb 2025Introducing step failure strategies in Bitbucket PipelinesIntroduces step failure strategies to Bitbucket Pipelines, allowing explicit control over pipeline behavior when a step fails. The initial release includes the 'ignore' strategy, which marks a failed step as 'Failed' in the UI but allows the pipeline to continue. Future strategies like retries and manual approvals are planned. The post details the configuration using the `on-fail` option with a `strategy` property and describes visual updates to indicate ignored failures. Limitations include no support for deployment steps and the inability to rerun completed steps with ignored failures.
Jan 2025Quickly diagnose issues by viewing previous Pipeline runsThis post introduces the capability to view previous pipeline runs directly within the Bitbucket Pipelines UI. This feature allows users to access the most recent 10 runs for a specific pipeline, compare results, track progress, and troubleshoot issues. The run number is now included in the URL for easy sharing and bookmarking.
Nov 2024Evolving Atlassian's deployment controls enforcementThis post details the evolution of Atlassian's deployment controls enforcement, moving from an implicit delegated trust model to a standardized artifact metadata store. Key technical contributions include: 1. **Artifact Metadata Store (Metadata-API):** Developed using Grafeas as inspiration, this component standardizes and centralizes artifact metadata. It supports storing signed attestations for builds, deployments, and custom claims. 2. **Build Data Collection:** Integrations with Bitbucket Pipelines (via a connect plugin and queue) and Bamboo Server (via a server plugin and Streamhub) collect build provenance. This includes build ID, commands, source provenance, and produced artifacts. 3. **Artifact Attestations:** Attestations are used to record observations about artifacts, linking them to their producing build and verifying compliance status. This includes ephemeral token creation for Artifactory uploads and direct event ingestion for other artifact stores like Config Registry and Bifrost. 4. **Standardized Metadata Structure:** A uniform data structure for build, deployment, and attestation metadata was established, enabling querying and filtering across diverse systems. 5. **Policy Decision Making & Enforcement:** The system centralizes policy decision-making and standardizes enforcement across deployment mechanisms, moving towards explicit verification at deployment time. 6. **Minimizing Developer Friction:** The design prioritizes minimal adoption requirements and avoids changes to build configurations, aiming for a 20,000+ hour positive impact on developer productivity.
Apr 2024Introducing Dynamic Pipelines: A new standard in CI/CD flexibilityThis post introduces Dynamic Pipelines, a new capability for Bitbucket Cloud Premium that allows users to create serverless functions using Forge to alter pipeline configurations in real-time before execution. This enables dynamic Docker image naming, pre-approved Docker image enforcement, self-hosted runner selection, selective test execution in monorepos, reusable CI/CD workflow blocks, cost attribution via runner tagging, and custom `bitbucket-pipelines.yml` syntax generation. It supports both repository-level and workspace-level configurations.
Jun 2021How Statuspage deploys continuously with Bitbucket and SleuthThis post details Statuspage's continuous deployment process, emphasizing the use of Sleuth for deployment coordination and health monitoring. It describes how Sleuth's 'locking' feature prevents merges outside designated times, improving developer sanity and preventing production issues. It also explains how Sleuth aggregates error and metric data from tools like Sentry and SignalFx to provide a unified view of deployment health, allowing developers to quickly identify and address unhealthy deployments.