TechPrufer
Get started
Atlassian
Atlassian logoAtlassian · Feature trail

Scheduled Pipelines

2 posts · Jan 2017 – Nov 2025

What this trail covers

Bitbucket Pipelines now supports dynamic step conditions based on boolean expressions evaluated during pipeline execution, allowing for more flexible and intelligent workflow control. This builds upon previous capabilities for manual triggers, Git tag triggers, and concurrency groups, enabling steps to be skipped or executed based on runtime variables, scan results, or combined conditions with file changesets. The system provides detailed logging for troubleshooting and handles race conditions a

All Atlassian trails
  1. Introducing Dynamic Step Condition for Bitbucket PipelinesIntroduces a new `state` condition type for Bitbucket Pipelines steps, allowing dynamic skipping based on boolean expressions evaluated during pipeline execution. This enables conditional logic using pipeline context variables (default, workspace, repository, deployment, and output variables from previous steps). Supports comparison operators, grouping, logical operators, and a `glob` function. Expressions must resolve to a boolean and are limited to 1000 characters. Detailed logging is provided for debugging. Addresses potential race conditions and specifies evaluation timing for automatic, manual, and retried steps.
  2. Reimagining how you structure workflows in Bitbucket PipelinesIntroduces a new top-level `triggers` property and `condition` blocks for defining event-driven rules that can execute multiple custom pipelines in parallel when conditions are met. This replaces the previous 'first match wins' behavior of traditional selectors. Supports logical expressions, comparisons, and `glob()` functions within conditions. Enhances pull request pipelines by allowing triggers based on destination branch and providing separate build statuses for each parallel pipeline run.
  3. Enhancements to Bitbucket Pipelines step conditionsIntroduces `excludePaths` as a new changeset condition for step and stage levels in `bitbucket-pipelines.yml`. This allows pipelines to skip steps or stages if changesets only contain files matching the specified glob patterns, enabling faster pipeline execution by avoiding unnecessary runs for low-impact file modifications.
  4. Scheduled pipelines now available in Bitbucket PipelinesIntroduces the ability to schedule Bitbucket Pipelines runs by defining custom pipelines in `bitbucket-pipelines.yml` and creating schedules for branches from the Pipelines view. Pipelines can be configured for hourly, daily, or weekly execution.
  5. 2 additional ways to trigger your builds in PipelinesThis post introduces two new ways to trigger Bitbucket Pipelines: manual triggers and tag-based triggers. Manual triggers are configured via a `custom` pipeline in `bitbucket-pipelines.yml` and can be invoked from the Bitbucket UI. Tag triggers are configured via a `tag` section in `bitbucket-pipelines.yml`, allowing pipelines to run when Git tags matching a specified pattern are pushed. The `BITBUCKET_TAG` environment variable is made available for tag-triggered builds.