Thoughts on DevOps, infrastructure, and engineering at scale.
Throughout this series I’ve been describing a system — self-hosted GitHub Actions runners with custom AMIs, autoscaling, and a Python runtime — without really addressing the elephant in the room. There’s one person managing all of this. Me.
Read moreThis is the post where I admit that I kept things in bash for too long.
Read moreIn Part 1 I explained how we run our entire CI on a single EC2 instance with 4 concurrent runner processes. In Part 2 I covered how we bake and promote AMIs without Packer. Both of those posts describe a...
Read moreIn Part 1 I talked about how we run our entire CI pipeline on a single EC2 instance with 4 concurrent runner processes. The secret ingredient was a custom AMI with our 23GB devcontainer image pre-baked into the Docker cache,...
Read moreLook, I’m not going to pretend I set out to build something clever here. I’m a DevOps engineer at a robotics startup. We needed CI that worked. GitHub-hosted runners didn’t. So I built something that did.
Read more