| date | title | author | weight | toc | aliases | description | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
2000-01-01 00:00:00 +0000 |
Overview |
bradrydzewski |
1 |
true |
|
Installation overview.
|
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.
Drone integrates seamlessly with popular Source Control Management providers. Please choose your provider to get started.
{{< link "/server/provider/github" >}} {{< link "/server/provider/gitee" >}} {{< link "/server/provider/gitlab" >}} {{< link "/server/provider/gogs" >}} {{< link "/server/provider/gitea" >}} {{< link "/server/provider/bitbucket-cloud" >}} {{< link "/server/provider/bitbucket-server" >}}
Drone server upgrades are meant to be simple and safe. Replace the old Docker image with the new Docker image and Drone will handle everything else (automatic database migrations, etc).
If a release introduces breaking changes or requires manual upgrade it will be specified in the release notes. As a general rule we try to maintain strict backward compatibility and avoid breaking changes, even in major releases.
# terminate the drone server
docker stop drone
docker rm drone
# pull the latest major release
docker pull drone/drone:2
# re-start the drone server using the
# newer docker image
docker run ... Drone Runners are standalone daemons that poll the server for pending pipelines to execute. There are different types of runners optimized for different use cases and runtime environments. Once the server is successfully installed you must install one or more runners.
{{< link "/runner/overview" "See the Runner Installation Guide" >}}