Why use templates?

Large organizations can have difficulty maintaining large numbers of build configuration files. Very often, those configuration files are very similar or almost identical across projects. Some changes need to be made across all projects, for example, needing to change the version of a docker image.

To make this simpler, Drone has build templates that can be shared across projects. A project can use a template and provide project-specific information to alter the build.

This will simplify configuration management at organizations that have large numbers of similar configuration files; it will reduce the complexity of YAML files in individual repositories and will simplify the management of configuration across repositories.

Templates use Go templating. For advanced usage, please see the documentation.

Here are the articles in this section:

Jsonnet Store and manage jsonnet templates per-organization. Starlark Store and manage starlark templates per-organization. Variables a list and description of variables available for use Yaml Store and manage yaml templates per-organization.