| .github | ||
| cmd/drone-server | ||
| core | ||
| docker | ||
| handler | ||
| livelog | ||
| logger | ||
| metric | ||
| mock | ||
| operator | ||
| plugin | ||
| pubsub | ||
| scheduler | ||
| scripts | ||
| server | ||
| service | ||
| session | ||
| store | ||
| trigger | ||
| version | ||
| web | ||
| .dockerignore | ||
| .drone.yml | ||
| .github_changelog_generator | ||
| .gitignore | ||
| BUILDING | ||
| BUILDING_OSS | ||
| CHANGELOG.md | ||
| go.mod | ||
| go.sum | ||
| HISTORY.md | ||
| LICENSE | ||
| NOTICE | ||
| Taskfile.yml | ||
Drone 
Welcome to the Drone codebase, we are thrilled to have you here!
What is Drone?
Drone is a continuous delivery system built on container technology. Drone uses a simple YAML build file, to define and execute build pipelines inside Docker containers.
Table of Contents
- What is Drone?
- Table of Contents
- Community
- Contributing
- Code of Conduct
- Setup Documentation
- Usage Documentation
- Example
.drone.ymlbuild file - Plugin Index
- Documentation and Other Links
Community
You can visit us at Discourse as well as our Slack.
Contributing
We encourage you to contribute to Drone! whether thats joining in on the community slack or discourse, or contributing pull requests / documentation changes or raising issues.
Code of Conduct
Drone follows the CNCF Code of Conduct.
Setup Documentation
This section of the documentation will help you install and configure the Drone Server and one or many Runners. A runner is a standalone daemon that polls the server for pending pipelines to execute.
Usage Documentation
Our documentation can help you get started with the different types of pipelines/builds. There are different runners / plugins / extensions designed for different use cases to help make an efficent and simple build pipeline
Plugin Index
Plugins are used in build steps to perform actions, eg send a message to slack or push a container to a registry. We have an extensive list of community plugins to customize your build pipeline, you can find those here.
Example .drone.yml build file.
This build file contains a single pipeline (you can have multiple pipelines too) that builds a go application. The front end with npm. Publishes the docker container to a registry and announces the results to a slack room.
name: default
kind: pipeline
type: docker
steps:
- name: backend
image: golang
commands:
- go get
- go build
- go test
- name: frontend
image: node:6
commands:
- npm install
- npm test
- name: publish
image: plugins/docker
settings:
repo: octocat/hello-world
tags: [ 1, 1.1, latest ]
registry: index.docker.io
- name: notify
image: plugins/slack
settings:
channel: developers
username: drone
Documentation and Other Links
- Setup Documentation docs.drone.io/installation
- Usage Documentation docs.drone.io/getting-started
- Plugin Index plugins.drone.io
- Getting Help discourse.drone.io
- Build the Enterprise Edition BUILDING
- Build the Community Edition BUILDING_OSS
Building from source
We have two versions available: the Enterprise Edition and the Community Edition
Release procedure
Run the changelog generator.
docker run -it --rm -v "$(pwd)":/usr/local/src/your-app githubchangeloggenerator/github-changelog-generator -u drone -p drone -t <secret github token>
You can generate a token by logging into your GitHub account and going to Settings -> Personal access tokens.
Next we tag the PR's with the fixes or enhancements labels. If the PR does not fufil the requirements, do not add a label.
Before moving on make sure to update the version file version/version.go && version/version_test.go.
Run the changelog generator again with the future version according to semver.
docker run -it --rm -v "$(pwd)":/usr/local/src/your-app githubchangeloggenerator/github-changelog-generator -u drone -p drone -t <secret token> --future-release v1.0.0
Create your pull request for the release. Get it merged then tag the release.