Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


drone (37) Versions 3.6.1

Installs/Configures Drone

cookbook 'drone', '= 3.6.1', :supermarket
cookbook 'drone', '= 3.6.1'
knife supermarket install drone
knife supermarket download drone
Quality 71%

Drone cookbook

Build Status

Installs Drone, a CI server built on Docker.

More information also @



  • Chef 12+


This cookbook is tested against:

  • Ubuntu 16.04
  • CentOS 7.x

...but it might work on other platforms.

If installing and managing docker with this cookbook only version 1.11+ is supported.




Installs the drone server.

Include recipe[drone::default] in your run list.


Fronts drone server with a reverse_proxy using nginx for HTTPS.

Include recipe[drone::reverse_proxy] in your run list.


Installs and sets up the drone worker. For use with Drone <= 0.4

Basically installs docker and exposes the socket over TCP for the Drone server to send builds to.

Include recipe[drone::worker] in your run list.


Installs and sets up the drone agent. For use with Drone >= 0.5

Include recipe[drone::agent] in your run list.


For Drone ENV config settings see:
* - Drone 0.4
* - Drone 0.5

Attribute Description Type Default
node['drone']['repo'] Docker repo to pull Drone from String 'drone/drone'
node['drone']['version'] Version of Drone String '0.4'
node['drone']['server']['port'] Host port to bind drone to Integer 80
node['drone']['server']['volumes'] Volumes to mount to drone from host Array ['/var/lib/drone:/var/lib/drone', '/var/run/docker.sock:/var/run/docker.sock']
node['drone']['vault']['bag'] Name of vault with secrets String 'vault_drone'. See Vault section below.
node['drone']['config'] Hash of Drone ENV configuration options Hash See Configuration section below.
node['drone']['agent']['config'] Hash of configuration options for Drone Agent Hash See Configuration section below.
node['drone']['disable_repo_activation'] Block ability to activate new repos through reverse proxy. Useful for trying to stop people from using an old Drone env. Boolean false


The configuration in Drone 0.4.0 changed from TOML to BASH RC file.

The minimum required attribute is to set following tokens for your "remote" driver (gitlab, github, etc..)

  • node['drone']['config']['oauth_client']
  • node['drone']['config']['oauth_secret']

See the drone documentations and attributes/default.rb for more options.


For drone::reverse_proxy you need:
* [certs](test/integration/data_bags/vault_drone/certs.json)

Other optional items include:
* drone_secret
* drone_github_client
* drone_github_secret
* database_config


See attributes/docker.rb for more options.

Note: There is no ability to control docker version on RHEL based platforms.


  • Linting - Rubocop and Foodcritic
  • Spec - ChefSpec
  • Integration - Test Kitchen

Testing requires ChefDK be installed using it's native gems.

gem install docker-api
foodcritic -f any -X spec .
rspec --color --format progress

If you run into issues testing please first remove any additional gems you may
have installed into your ChefDK environment. Extra gems can be found and removed
at ~/.chefdk/gem.

Drone Cookbook Changelog


  • Updates to work properly in Chef 13


  • Allow specifying volumes to mount into Drone from host with node['drone']['server']['volumes']
  • Minor Breaking: specifying host port to bind Drone to with node['drone']['server']['port']
    • Decided to do this since 3.5.0 has been released for 30min now and this makes more sense and don't wanna major version bump. Sorry!


  • Allow specifying host port to bind Drone to with node['drone']['port']


  • Allow setting drone container to use with node['drone']['repo']. Default is drone/drone which is what was previously hardcoded.


  • Allow setting node attributes node['drone']['repo_activation_org_whitelist'] to whitelist orgs for repo activation when node['drone']['disable_repo_activation'] is set to true


  • Allow setting node attribute node['drone']['disable_repo_activation'] to disable ability to activate new repos



  • For newer version of Docker need to use new resource in docker cookbook for installing while specifying a version


  • Fix reverse proxy for Drone 0.5


  • Add ability to set docker daemon logging level


  • Allow bypassing loading secrets on chef-vault failure (permissions)


  • Fix allowing user to specify docker version


  • BREAKING CHANGE (maybe): No longer pin version of docker to install by default. You still can do it if you want manually though.


  • Support for CentOS 7.x


  • Remove DEPRECATED drone token secrets management items
  • Added drone_secret support


  • Allow drone_github_client to be in a Vault


  • Attributize logging for Drone containers


  • Allow specifying version of drone to use
  • Added drone::agent recipe for installing Drone 0.5 agent
  • Added ability to apply secrets drone_agent_secret, drone_token, drone_github_secret and database_config from vault


  • BREAKING CHANGE: Move Drone app config items to node['drone']['config']
  • BREAKING CHANGE: Removed package install method as it's not supported
  • Added drone::reverse_proxy recipe to be able to front Drone with HTTPS via a reverse proxy
  • Added drone::worker recipe to be able to create additional systems to run drone builds on
  • Version bump on docker community cookbook
  • Make docker_container resource sensitive to prevent displaying secrets passed through ENV to drone


  • BREAKING CHANGE: Use drone containers rather then installing drone package by default
  • Add ability to deploy drone using drone docker container


  • Uses docker version from attributes (default 1.8.3)
  • Specify docker tls certs or use self-generated


  • Deploy Drone v0.4.0 (a dev branch)
  • Add dronerc template
  • Add docker recipe to install docker from cookbook
  • Add update recipe to update docker images
  • For integrations generates docker self-signed certs


  • Docker can now be disabled (Graham Weldon)
  • Fix registration option - moving to each VCS config (Graham Weldon)
  • Extend / improve README documentation


  • Configure Drone with TOML (Graham Weldon)
  • Use new Drone package URL (Ke Zhu)


  • Add Apache 2.0 license
  • Fix options being passed to droned (Ross Timson)
  • Numerous development/test improvements (Ross Timson)


  • Settable drone_tmp (Eric Buth)


  • Add ability to specify custom drone options (Brint O'Hearn)


  • Initial Drone cookbook (Justin Campbell)

Collaborator Number Metric

3.6.1 passed this metric

Contributing File Metric

3.6.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

3.6.1 passed this metric

License Metric

3.6.1 passed this metric

No Binaries Metric

3.6.1 passed this metric

Testing File Metric

3.6.1 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

3.6.1 passed this metric