When you push code to your repository, open a pull request, or create a tag, your source control management system automatically sends a webhook to Drone which in turn triggers pipeline execution. Use the triggers section to limit pipeline execution.

Example limits pipeline execution by branch:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

kind: pipeline
type: digitalocean
name: default

server:
  host: 1.2.3.4
  user: root
  password:
    from_secret: password

steps:
- name: build
  commands:
  - go build
  - go test

trigger:
  branch:
  - master

You can use wildcard matching in your triggers. Note that triggers use glob pattern matching, not regular expressions.

17
18
19
20
21

trigger:
  ref:
  - refs/heads/master
  - refs/heads/**
  - refs/pull/*/head

You can also combine multiple triggers. Note that all triggers must evaluate to true when combining multiple triggers.

17
18
19
20
21

trigger:
  branch:
  - master
  event:
  - push

By Branch

The branch trigger limits step execution based on the git branch. Please note that the target branch is evaluated for pull requests; and branch names are not available for tag events.

17
18
19
20

trigger:
  branch:
  - master
  - feature/*

Example include syntax:

17
18
19
20
21

trigger:
  branch:
    include:
    - master
    - feature/*

Example exclude syntax:

17
18
19
20
21

trigger:
  branch:
    exclude:
    - master
    - feature/*

By Event

The event trigger limits step execution based on the drone event type. This can be helpful when you want to limit steps based on push, pull request, tag and more.

17
18
19
20
21
22
23

trigger:
  event:
  - push
  - pull_request
  - tag
  - promote
  - rollback

Example include syntax:

17
18
19
20
21

trigger:
  event:
    include:
    - push
    - pull_request

Example exclude syntax:

17
18
19
20

trigger:
  event:
    exclude:
    - pull_request

By Reference

The reference trigger limits step execution based on the git reference name. This can be helpful when you want to glob match branch or tag names.

17
18
19
20

trigger:
  ref:
  - refs/heads/feature-*
  - refs/tags/*

Example include syntax:

17
18
19
20
21
22

trigger:
  ref:
    include:
    - refs/heads/feature-*
    - refs/pull/**
    - refs/tags/**

Example exclude syntax:

17
18
19
20
21
22

trigger:
  ref:
    exclude:
    - refs/heads/feature-*
    - refs/pull/**
    - refs/tags/**

By Repository

The repository trigger limits step execution based on repository name. This can be useful when Drone is enabled for a repository and its forks, and you want to limit execution accordingly.

17
18
19

trigger:
  repo:
  - octocat/hello-world

Example include syntax:

17
18
19
20
21

trigger:
  repo:
    include:
    - octocat/hello-world
    - spacebhost/hello-world

Example exclude syntax:

17
18
19
20
21

trigger:
  repo:
    exclude:
    - octocat/hello-world
    - spacebhost/hello-world

Example using wildcard matching:

17
18
19
20

trigger:
  repo:
    include:
    - octocat/*

By Instance

The instance trigger limits step execution based on the Drone instance hostname. This can be useful if you have multiple Drone instances configured for a single repository, sharing the same yaml file, and want to limit steps by instance.

17
18
19
20

trigger:
  instance:
  - drone.instance1.com
  - drone.instance2.com

Example include syntax:

17
18
19
20
21

trigger:
  instance:
    include:
    - drone.instance1.com
    - drone.instance2.com

Example exclude syntax:

17
18
19
20
21

trigger:
  instance:
    exclude:
    - drone.instance1.com
    - drone.instance2.com

Example using wildcard matching:

17
18
19
20

trigger:
  instance:
    include:
    - *.company.com

By Status

The status trigger limits step execution based on the pipeline status. For example, you may want to configure Slack notification only on failure.

17
18
19

trigger:
  status:
  - failure

Execute a step on failure:

17
18
19

trigger:
  status:
  - failure

Execute a step on success or failure:

17
18
19
20

trigger:
  status:
  - success
  - failure

The following configuration is redundant. The default behavior is for pipeline steps to only execute when the pipeline is in a passing state.

17
18
19

trigger:
  status:
  - success

By Target

The target trigger limits step execution based on the target deployment environment. This only applies to promotion and rollback events.

17
18
19

trigger:
  target:
  - production

Example include syntax:

17
18
19
20
21

trigger:
  target:
    include:
    - staging
    - production

Example exclude syntax:

17
18
19
20

trigger:
  target:
    exclude:
    - production