Add Details on Woodpecker targets & comparison WP/Actions (#635)

This is targeted to close both #545 and #595 by

* explicitly mentioning the Woodpecker target
* link to the actions meta repo that provides some overview on Actions & Woodpecker

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/635
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
Co-committed-by: Bastian Greshake Tzovaras <bgreshake@googlemail.com>
This commit is contained in:
Bastian Greshake Tzovaras 2025-07-02 16:27:43 +02:00 committed by Panagiotis "Ivory" Vasilopoulos
parent 9b85081adf
commit d17122d241

View file

@ -43,6 +43,7 @@ For the usage of our Woodpecker instance, keep the following in mind:
resource usage therefore.
- The CI service requires manual onboarding and Woodpecker has limited Role-Based Access Control (RBAC) capabilities,
which will be a problem for projects with a team-based permission structure or many individual collaborators.
- `linux/amd64` is the sole build target on the Woodpecker CI deployment.
Issues and general feedback should be reported in our
[dedicated Codeberg CI feedback repository](https://codeberg.org/Codeberg-CI/feedback).
@ -69,5 +70,8 @@ for more information.
## Using Forgejo Actions
Forgejo, the software Codeberg is built on, offers a CI/CD feature called Actions.
Forgejo Actions can be used with self-hosted runners and Codeberg also provides a hosted version in a limited fashion in open alpha.
Further information such as how to run it is available in [Using Forgejo Actions (Self-hosted) page](./actions).
Further information such as how to run Forgejo Actions is available in [Using Forgejo Actions (Self-hosted) page](./actions).
If you want to learn more about the differences between the Woodpecker CI and Forgejo Actions, you can [find those on the actions meta repository](https://codeberg.org/actions/meta).