100% Free Forever
AI-Powered Learning
Industry Expert Content
Certificates & Badges
Learn At Your Own Pace
DevOps

Drone CI

IntermediateTool3.6K learners

Drone is a container-native continuous integration and delivery platform where every pipeline step runs inside its own Docker container, configured through a simple YAML file.

Definition

Drone is a container-native continuous integration and delivery platform where every pipeline step runs inside its own Docker container, configured through a simple YAML file.

Overview

Drone's core idea is that CI/CD pipelines should be built entirely out of containers: each step in a `.drone.yml` pipeline file specifies a container image to run, and Drone executes that step inside an isolated container with the repository checked out, rather than running commands directly on a shared build host. This containers-all-the-way-down model makes pipelines portable and reduces the 'works on my machine' problems that can come from build-agent configuration drift. Drone integrates with source control platforms like GitHub, GitLab, and Bitbucket to trigger pipelines on events such as pushes and pull requests, and it supports a plugin marketplace of prebuilt containerized steps (for tasks like publishing a Docker image, deploying to a cloud provider, or sending notifications) that can simply be referenced by image name in the pipeline YAML rather than installed as server plugins. Originally an independent open-source project, Drone was acquired by Harness, which continues to offer it both as a standalone open-source CI system and as part of its broader delivery platform, making it a common lightweight choice for teams that want Docker-native pipelines without the operational overhead of larger CI systems. It is often mentioned alongside Jenkins in this space. It is often mentioned alongside GitLab CI in this space.

Key Features

  • Every pipeline step runs inside its own Docker container
  • Simple, declarative .drone.yml pipeline configuration
  • Plugin marketplace of prebuilt containerized steps for common tasks
  • Native integration with GitHub, GitLab, and Bitbucket for triggering pipelines
  • Portable pipelines that avoid build-agent configuration drift
  • Lightweight footprint compared to larger, plugin-heavy CI servers

Use Cases

Running Docker-native CI/CD pipelines with reproducible, isolated build steps
Building, testing, and publishing container images as part of a pipeline
Triggering automated builds from GitHub, GitLab, or Bitbucket events
Deploying to cloud providers using prebuilt marketplace plugin steps
Providing a lightweight self-hosted CI alternative to larger platforms

Frequently Asked Questions