Ci on My personal blog

Splitting Rust builds and tests on Codeberg

Tue, 30 Jun 2026 00:00:00 +0000

After I got building containers on Codeberg sorted out, the next thing that broke on me was much more boring on paper: the test job kept getting killed.

Not failing. Killed.

The logs would scroll happily through compilation and a few dozen passing tests, and then the runner would just cut the job off mid-run with a deadline error.

So this post is about that: what to do when your Rust test suite is simply too slow to fit inside a single hosted CI job, and the runner has opinions about how long it will wait for you.

When Let's Encrypt Is Valid but GitHub Actions Still Rejects It

Wed, 10 Jun 2026 00:00:00 +0000

A few days ago I ran into a surprisingly tricky TLS issue while setting up automated tests for a service running behind Let’s Encrypt certificates.

The symptoms were confusing at first:

Browsers accepted the certificate.
curl --insecure worked.
The certificate looked perfectly valid.
Yet GitHub Actions consistently failed with:

SSL certificate problem: unable to get local issuer certificate

At first glance this looked like a classic missing intermediate certificate problem.

Building containers on Codeberg

Sun, 15 Mar 2026 00:00:00 +0000

I have been moving more and more of my smaller projects over to Codeberg lately.

For plain git hosting and Forgejo based CI, it is a very pleasant setup. The one area where I had to do a bit more work than expected was container builds.

At first glance this looks like it should be boring:

write a Dockerfile
add a CI step
build the image

But on a hosted Codeberg runner this is exactly the type of thing where the defaults are not quite the defaults you may be used to from GitHub Actions or from your own machine.

Letting an LLM Review Our Pull Requests (So You Don’t Have To)

Fri, 08 Aug 2025 00:00:00 +0000

This post is a cross-post from Down to Zero. Canonical source: https://downtozero.cloud/posts/2025/pr-reviews/

We love automation. We use it to power our infrastructure, to scale workloads down to zero, and—increasingly—to shrink the amount of human attention needed to ship high-quality code. One place that still felt stubbornly manual was pull-request reviews. Between Cursor as our IDE, ChatGPT/Codex for prototyping, and gemini-cli for quick checks, our local workflows were fast—but CI still waited for a human.

A Solar Powered GitHub Runner

Sat, 15 Apr 2023 09:08:05 +0000

This is a cross-posting from downtozero.cloud

The more our little project progresses, the more code we produce. And like most of our community these days, we host our code on GitHub.

So during development we discussed the implications of a DownToZero architecture for something like a GitHub process. We quickly identified two types of actions that need to be performed on the infrastructure.

The first is the CI build, which should always provide immediate feedback to the developer. It checks for compliance as well as code integrity and is usually deeply involved in the development process. These jobs are time-sensitive because someone is usually waiting for them.