mirror of
https://github.com/fbartels/cloudron-drone-app.git
synced 2024-11-21 12:50:59 +00:00
Run drone-server on Cloudron
0ac667af18
This also updates the gear and adds an optional bash script instead of the Makefile Signed-off-by: Felix Bartels <felix@9wd.eu> |
||
---|---|---|
.github | ||
helpers | ||
runner | ||
.dockerignore | ||
.drone.yml | ||
.gitignore | ||
CloudronManifest.json | ||
Dockerfile | ||
LICENSE.txt | ||
logo.png | ||
Makefile | ||
POSTINSTALL.md | ||
README.md | ||
start.sh | ||
supervisor-drone-server.conf |
Drone CI for Cloudron
Run the Drone server on Cloudron and the agents locally.
I use this setup together with a Gitea running on the same Cloudron installation.
Requirements
docker compose
(on the system you want to run the agent on)git
jq
make
- Cloudron CLI
Installation
- Run
DOCKER_REPO=your-docker-hub-user make install
to install the Drone server component atdrone.yourdomain.com
(yourdomain.com
will adapt automatically to your Cloudron setup). - Run
make exec' to open the app's CLI and modify the
.env' so that it can connect to your Git instance.- See https://readme.drone.io/server/provider/gitea/#create-an-oauth-application for information on OAuth registration in Gitea.
- The drone instance runs at
drone.yourdomain.com
and the redirect URL would behttps://drone.yourdomain.com/login
. - The secrets are automatically created and added to the
.env
file.
- Run
cloudron restart
to restart the application and apply your changes. - Check that your setup works by going to
https://drone.yourdomain.com
. - If all looks good, run `runner/start.sh' to start the Drone agent on your local machine (it will grab the credentials directly from the installed app).
- Add the drone configuration to your desired repositories
Tips and tricks
I would also like to share some very useful commands. To install the drone
CLI, follow the official docs.
Using drone-cli
Go to your user settings and get the login information
export DRONE_SERVER=https://drone.9wd.eu
export DRONE_TOKEN=your token
drone info
Running pipelines directly
You can also run pipelines directly from the Drone CLI:
drone exec --secret-file secrets.txt .drone.yml
A template for secrets.txt
:
slack_url=https://hooks.slack.com/services/xxxxxxxxxxxx
Adding secrets from the CLI
You can either add secrets via the web interface or use drone directly from your terminal:
drone secret add -repository username/repository-name --name foo --data bar --allow-pull-request
Trigger build via curl
curl -X POST -i https://drone.9wd.eu/api/repos/felix/cloudron-drone-app/builds -H "Authorization: Bearer your-token"
Get token from https://drone.9wd.eu/account
Webhooks do not trigger builds in drone?
- Remove the webhook in Gitea
- Go to the Drone dashboard and disable the individual project in the settings.
- re-enable the project
- Go back to Gitea and "test delivery" your new webhook.
Inspiration
- Setting up a simple, self-hosted & fast CI/CD solution with Drone.io](https://webhookrelay.com/blog/2019/02/11/using-drone-for-simple-selfhosted-ci-cd/)
- Official Drone documentation](https://docs.drone.io/server/provider/gitea/)