Drone · Rate Limits

Drone Ci Rate Limits

Drone is self-hosted; the open-source server does not enforce a managed rate quota. Operational limits are configured via DRONE_* environment variables (queue length, concurrent runners, log buffer size) and by the capacity of the host. The upstream Git provider (GitHub/GitLab/Bitbucket/ Gitea) imposes its own rate limits on Drone's webhook/SCM client.

3 Limits
DevOpsCI/CDContainer-NativeOpen SourceYAMLRate LimitingQuotasThrottling

Limits

Concurrent runners server
concurrent_jobs
see DRONE_RPC_HOST / runner concurrency settings
Bounded by registered runners and DRONE_RUNNER_CAPACITY.
Build log buffer build
bytes
see DRONE_LOGS_TEXT
Configurable build-log retention and streaming buffer.
SCM provider rate limits scm_account
requests
per upstream SCM (GitHub 5,000/h authed, etc.)
Drone defers to the upstream Git provider's REST/Git rate limits.

Policies

Backoff Strategy
Drone's webhook handler retries SCM calls on 429/5xx with backoff.
Capacity Planning
Scale runners horizontally; size DRONE_RUNNER_CAPACITY per host.

Sources