Branch Configuration

You can use branch patterns to ensure pipelines are only triggered when necessary. This guide shows you how to set up branch patterns for whole pipelines and individual build steps.

In step-level and pipeline-level branch filtering you can use * as a wildcard, and ! for not, as shown in the examples. If you want a full range of regular expressions that operate on more than just branch names, take a look at the conditionals page.

Pipeline-level branch filtering

By default a pipeline will trigger builds for all branches (* or blank). In your pipeline settings you can set specific branch patterns for the entire pipeline. If a commit doesn't match the branch pattern, no build will be created.

Pull Request Builds

Builds created for pull requests will ignore any pipeline-level branch filters. If you want to limit the branches that can build pull requests, add an additional branch filter in your pipeline's source control settings.

This filter can be found under 'Build pull requests' if you have chosen the 'Trigger builds after pushing code' option.

Step-level branch filtering

As with pipeline-level branch filtering, you can set branch patterns on individual steps. Steps that have branch filters will only be added to builds on branches matching the pattern.

For example, this pipeline.yml file demonstrates the use of different branch filters on its steps:

  - label: "🔨 Build"
      - "npm install"
      - ""
    branches: "feature/* release/* master !infrastructure"
  - block: "Release notes"
    prompt: "Please add notes for this release"
      - text: "Notes"
        key: "notes"
    branches: "release/*"
  - label: "Deploy Preparation"
    command: ""
    branches: "master"
  - wait
  - trigger: "app-deploy"
    label: ":shipit:"
    branches: "master"

Step-level branch filters will only affect the step that they are added to. Subsequent steps without branch filters will still be added to the pipeline.

Branch pattern examples

When you define a value in the branch attribute of a step, only builds on the specified branch/es will contain that step. Adding more values to the branch attribute will expand the set of branches that will include that step.

The following are examples of patterns, and the branches that they will match:

  • master production will match master and production only
  • master features/* will match master and any branch that starts with features/
  • */release-123 will match any branch that ends with /release-123 such as feature-123/release-123
  • v*.0 will match branch that begins with a v and ends with a .0, such as v1.0
  • v*.*.* will match branch that begins with a v and has two periods, such as v1.2.3
  • !production will match any branch that's not production
  • staging !production development will match staging and development only

For more advanced step filtering, see the Using conditionals guide.