One of the first questions to answer when building out GitHub Actions compute on premises is “how do I know what my users are doing?” In an old-school persistent-machine setup, this isn’t a proble...

Now that we have a working Kubernetes cluster with the new actions-runner-controller scaling set of runners using the default image (Dockerfile and image), let’s create a couple of GitHub Actions t...

Kubernoodles is a reference architecture for a lot of “how to devops” things, mostly for actions-runner-controller within a larger business. With all the new work GitHub has put into the project, ...

GitHub Actions is one of the most popular CI tools in use today. If you need or want to run it yourself, though, there are a lot of design choices to make and not a lot of guidance. The most popu...

This piece is going to take a look at what this feature is and a quick overview of how it works, then go through some key decisions you should think through as you set it up. A bunch of experience...

A devcontainer lets you use an arbitrary Docker container as a development environment - leveraging the reproducible, version-controlled, and disposable nature of containers for a consistent develo...

Even though git is one of the most common software programs used in development, I’m continually impressed both at how customizable it is and how often it isn’t customized at all! There are severa...

This post is slides + commentary from a talk I gave at Cloud Native Colorado on November 21st, 2022 about some of the weird ways you can blow up your cluster and your sanity once continuous integra...

An interesting problem came my way not too long ago about how to undo a code change when a job fails in GitHub Actions. Since this job is triggered on a commit, we’d have to use git revert to crea...

Continuing from part 1 and part 2, there’s a moment where it looks like it might be cheaper to run your own build farm. I’m not going to talk numbers here - at all. The price of hardware and powe...