#forgejorunner — Public Fediverse posts

Forgejo Runner, the program executing workflows of continuous integration in #Forgejo, has been released in version 13.0. It comes with breaking changes that may break current workflows for Forgejo Actions users. These changes improve security, predictability, and maintainability. https://forgejo.org/2026-08-runner-release-v13/

#ForgejoRunner #ForgejoActions #CI

@electret nice, I‘m currently also experimenting with #k3s controlled through #ArgoCD with a self hosted #Forgejo. #renovatebot updates the helm chart of the #appOfApps each night and creates pull requests which gets validated by a #forgejorunner worklow before merging. Still at the beginning of the journey from single host docker to a cluster though.

I again spend two days of digging into (self-hosted) CI.

It is shocking how software development is dependent on #GitHub, their action runners and hosting of libraries!

I try to avoid it. For most projects I use #CodeBerg. Codeberg CI-support gets better and the public runners they offer are already quite good. The situation already has improved so much over the last two years.

I wanted reproduceable tests that also run in the CI, exactly the same way. In my case this requires the CI job to span up containers: docker-in-docker. This is not something Codeberg offers, so again I tried to configure my self-hosted forgejo-runner. The documentation is still a heavy read and there are no clear guidelines at all. I went from one error to the next for two days straight. In the end I gave up, I could not get directories from the job container mounted correctly in the containers started by the job container.

If anyone would offer help, I would take any advice.

#Forgejo #ForgejoRunner

It doesn't look like much but what you see here is a (finally) successful workflow running entirely locally on #Forgejo. It involved a lot of learning like #Synology's docker cannot really do DinD (or I couldn't find how), or how to configure #ForgejoRunner, or what kind of mini PC do people buy for #homelab servers, or how to install #Docker on #Proxmox, etc.
This makes my little Forgejo a lot more interesting that it used to!

Testing WordPress plugins using Forgejo Actions

Preface: Almost all public WordPress plugin development takes place on GitHub. We also collaborate on GitHub. However, we want to use and promote free alternatives for our own project. We currently host our own forgejo instance, but have been thinking about moving our repositories to @Codeberg, where we are more likely to find contributors and bug reports until the forgejo federation is more mature.

Automated Testing Workflows: It took us a long time to set up working workflows that run integrations tests with WordPress and the WordPress ActivityPub-plugin within Forgejo Actions using the Forgejo-Runner. Copy pasting the GitHub Actions workflow from for instance the ActivityPub plugin was just the beginning of an almost ten hour long debugging session. But now the tests are working.

#ForgejoActions #ForgejoRunner #Forgejo #PHPCS #PHPUnit #WordPress