TiloBox
Back to directory
Drone project preview

Drone

Container-native Continuous Integration platform built on Docker and Go by Harness.

LicenseApache-2.0
GitHub stars32.0k
Last commit1 weeks ago
Tags6 topics
Docker PipelinesGit Webhook CiDevops InfrastructureHarnessContainer CiGolang
Overview

Why consider Drone?

Drone is an open-source container-native continuous integration and delivery system. Written in Go, it executes every pipeline step inside an isolated Docker container, configured via simple YAML files with seamless GitHub, GitLab, and Gitea integration.

Guided learning

Learn Drone by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Drone

Drone eliminates dependency conflicts on build runners by executing every pipeline stage within ephemeral Docker containers.

Running with Docker

bash
1docker run -d \
2 --name=drone \
3 -p 80:80 \
4 -e DRONE_GITHUB_CLIENT_ID=your_id \
5 -e DRONE_GITHUB_CLIENT_SECRET=your_secret \
6 drone/drone:2

Drone is licensed under the Apache License Version 2.0.

Related tools

More options with a similar category or technology profile.

Drone FAQs

Drone is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Drone is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Drone is listed as an alternative to Jenkins. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.