Working with Codeberg's CI
Every piece of code should be tested regularly. Ideally developers already implement unit-tests to test the functionality of code sections. Some projects even implement a suite of integration tests, testing whether the code in different parts of the software works as a whole and (still) provides the functionality the software promises to deliver. Running these tests regularly (or continuously) is the job of a Continuous Integration solution. The results of the tests are displayed to the project members and maintainers, enabling them to identify problems and react if errors occur.
Using Codeberg's instance of Woodpecker CI
Codeberg currently provides an instance of Woodpecker CI to everyone who needs it. You need to request access, because we want to keep resource abuse minimal. Please check out our request procedure!
For the usage of our Woodpecker instance, keep the following in mind:
- CI access is provided as-is and might break at any time and for an undefined period of time, due to server issues, for testing and maintenance purpose or human error. Our CI service is not of the highest priority right now.
- Resource usage must be reasonable for the intended use-case. This is determined on a case-by-case basis, but please be aware that CI uses a lot of computing resources (cloning your repo and container, installing all your required tools, building and throwing everything away) which costs us money and does damage to our precious environment. Therefore, please consider twice how to create a good balance between ensuring code quality for your project and resource usage therefore.
- The service is in an early phase, which means it might not yet be suited for large and complex projects. Please report all issues you face to us, so you can be a part of the improvement!
If you are just curious about Woodpecker or already got access to a Woodpecker instance, the Woodpecker project has a great documentation on how to use Woodpecker in your repositories. For now, refer to the Gitea VCS integration section.
Using Codeberg / Forgejo / Gitea Actions
Forgejo, the software Codeberg is built on, offers a CI/CD feature called Actions. It offers compatibility with GitHub Actions, with some differences.
Further information such as how to run it is available in Using Forgejo / Gitea Actions (Self-hosted) page.
Hey there! 👋 Thank you for reading this article!
Is there something missing, or do you have an idea on how to improve the documentation? Do you want to write your own article?
You're invited to contribute to the Codeberg Documentation at its source code repository, for example, by adding a pull request or joining in on the discussion in the issue tracker.
For an introduction on contributing to Codeberg Documentation, please have a look at the Contributor FAQ.
© Codeberg Docs Contributors. See LICENSE