Updated 2 years ago by Admin

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:

1 ---
2 kind: pipeline
3 type: docker
4 name: default
6 steps:
7 - name: backend
8 image: golang
9 commands:
10 - go build
11 - go test
13 - name: frontend
14 image: node
15 commands:
16 - npm install
17 - npm run test
19 ...

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

How did we do?