Table of Contents
We host Woodpecker CI at https://ci.exozy.me. But watch out: Our instance is a bit weird, because it's patched to run pipelines as your user on our server, not in a container. You should think of our CI as an automation tool, not a CI, since it doesn't give you a pristine, clean environment for each build. Although if you want a clean environment, you can make your pipeline run a container.
Usage
You can find example build pipeline here and here. Repos are cloned to ~/.cache/woodpecker/reponame, so you can SSH into exozyme and inspect failed builds.
Pipeline image
Since our instance doesn't use containers, you should not specify a container image for the image field. Instead, you should pass one of the shells available in the system (ex. bash, fish) to run your pipeline.
Tips and tricks
Use systemd in pipeline
Add export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus to your pipeline before the systemctl commands.