Self-Hosted Runners

You can add your own agents/runners to process CI/CD jobs for your repositories.

Crow CI

Follow the documented process to add a new “public” runner from the Crow CI docs.

Use the following addresses in the agent config:

CROW_SERVER: ci.codefloe.com
CROW_GRPC_ADDR: grpc.ci.codefloe.com

You can set additional CROW_AGENT_LABELS. By default, the agent will be restricted to the Crow org_id for which you created the agent token in the Crow UI.

Danger

It is not possible to configure an agent to process builds of multiple users/organizations. You need to add multiple agents to achieve this.

Avoiding Rate Limiting

When you starting processing builds on your own agent(s), you might run into rate-limiting (429 http errors) soon. To avoid this, please open a PR add the IPs of your agents to the fail2ban playbook of CodeFloe’s infra configuration following the existing entries.

Forgejo Actions

There’s an existing guide in the Codeberg Documentation which can be followed to add a self-hosted runner for Actions. Make sure to use https://codefloe.com as the argument for the --instance flag.

Ansible Role

Besides the deployment methods listed in Codeberg’s documentation, there is also an Ansible role forgejo_runner in the devxy.cicd collection, which is used to deploy the hosted runner on CodeFloe.