Skip to content
Back to Stack Recommender

Drone CI

Drone — container-native CI/CD pipeline platform.

DevOpsModerate

Stack Components

CI/CDDrone 2.x

Why

Every step runs in a Docker container, isolated and reproducible. Docker is used by 59% of professional developers per the Stack Overflow 2024 survey, and Terraform is used by 65% of organizations for IaC (HashiCorp 2024).

GitOps (ArgoCD, Flux) reduces deployment drift to near-zero by making git the single source of truth.

When

Use for Docker-based CI/CD. Avoid for non-containerized environments.

How

1. Deploy Drone server 2. Install drone CLI 3. Create .drone.yml 4. Activate repo 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

kind: pipeline type: docker steps: - name: test image: node:20 commands: [npm test]

Common Problems

  • ⚠Secrets not injected — check Drone secret management
  • ⚠Docker-in-Docker issues — use privileged mode carefully
  • ⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

  • ✓Use Drone plugins for common tasks
  • ✓Pin container image versions for reproducibility
  • ✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Drone CI and what projects is it for?

Drone — container-native CI/CD pipeline platform. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Drone CI in 10 minutes?

Two steps: (1) Deploy Drone server; (2) Install drone CLI. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Drone CI and how do I avoid it?

The most common pitfall is: Secrets not injected — check Drone secret management. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Drone CI?

Best practices for Drone CI include: Use Drone plugins for common tasks; Pin container image versions for reproducibility; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use Drone plugins for common tasks" — should be set up at project init to avoid costly rework later.

When should I NOT choose Drone CI?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Drone CI shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.