Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time
date title author weight aliases description
2000-01-01 00:00:00 +0000
Overview of Pipeline configuration.

Pipelines help you automate steps in your software delivery process, such as initiating code builds, running automated tests, and deploying to a staging or production environment.

Pipeline execution is triggered by a source code repository. A change in code triggers a webhook to Drone which runs the corresponding pipeline. Other common triggers include automatically scheduled or user-initiated workflows.

Pipelines are configured by placing a .drone.yml file in the root of your git repository. The yaml syntax is designed to be easy to read and expressive so that anyone viewing the repository can understand the workflow.

Example pipeline configuration:

{{< highlight yaml "linenos=table" >}}

kind: pipeline type: docker name: default


  • name: backend image: golang commands:

    • go build
    • go test
  • name: frontend image: node commands:

    • npm install
    • npm run test

... {{< / highlight >}}

Drone supports different types of pipelines, each optimized for different use cases and runtime environments:

{{< link "pipeline/docker/overview" "Docker Pipelines" >}} {{< link "pipeline/kubernetes/overview" "Kubernetes Pipelines" >}} {{< link "pipeline/exec/overview" "Exec Pipelines" >}} {{< link "pipeline/ssh/overview" "SSH Pipelines" >}} {{< link "pipeline/digitalocean/overview" "Digital Ocean Pipelines" >}} {{< link "pipeline/macstadium/overview" "MacStadium Pipelines" >}}