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

I just spent part of the day to unhinge my #forgejorunner to be able to deploy my #hugo blog automatically. I found several problems on the way, one of them being me setting $HOME path manually (and wrong). While my previous workflow was pretty fast as is, and I save like at most 30 seconds, this should at least make it harder to screw up or forget about things.

Now I just need to create a blog post every other day in order to make this worth it.
#xkcd

Go team is part of the master, pull gently and enjoy fully unvendored fresh #Kubo and default #Golang 1.24 in #Guix 

https://codeberg.org/guix/guix/commit/768d05fd3574038fcea985a5f5740a360430fac7

https://codeberg.org/guix/guix/commit/055e855828970b43875b15bf71d9a6528c2d751c

Thanks Maxim Cournoyer

Let's refresh #Docker and #ForgejoRunner in the next round?

Patches are welcome

#guixgoteam

My #forgejorunner broke after a recent update. Spent quite a while troubleshooting, running test actions, even rebuilding the runner box from scratch.

It wasn't using the configuration file I was modifying. Evidently, it _never_ used the config file, because I never started it properly in the past, and the defaults worked for me. It had been a while since I upgraded, so one of the default settings changed (automounting the Docker socket), which broke building containers.

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

#ForgejoRunner #Forgejo

idk what's up

https://0x0.st/XVyo.txt

Why do #Forgejo Actions get stuck at trying to clone from anywhere else than the official forgejo repo????

#ForgejoActions #ForgejoRunner