We are rolling out new documentation at docs.drone.io.
The good news is the documentation is much more detailed and comprehensive. We have even published formal specifications for our yaml syntax!
The bad news is that we expect some initial confusion due to the fact that Drone now supports multiple types of pipelines, where each type of pipeline defines its own unique yaml syntax. For example:
- the docker runner executes commands in docker containers
- the exec runner executes commands directly on the host machine (no docker involved)
- the ssh runner executes commands on a remote server (no docker involved)
- the digitalocean runner creates a digital ocean instance per-pipeline and executes commands directly on the vm (no docker involved)
Overall I am really excited to support different types of pipelines. There are many workloads and use cases that are poorly suited for containers, such as macOS builds. There are also certain workloads that are better suited for traditional virtual machines instead of containers. Drone will now be able to support these projects.
The challenge is that support for different runners and pipeline types adds a new dimension of complexity to the documentation. I found it very difficult to structure the documentation and very difficult to explain these concepts to readers, and route them to the appropriate pipeline or runner documentation.
The full documentation will be published to GitHub this week (most of the documentation is already published) and we hope people will help us improve the structure and clarity. We understand there will be some growing pains the first few weeks, and we appreciate your help and patience as we gather feedback and make improvements.
Finally, please be constructive with feedback. If you are going to comment on the quality of the documentation, please be sure to provide us with actionable feedback and examples of things that can be improved. Thanks!