Elektrine lite

← Feed

@coderanger@cloudisland.nz

Post #1809420

2026-04-28 19:56 UTC

Preface: This is not a dunk or an I Told You So. It is a reminder that other (better?) worlds can exist. GitHub Actions is clearly all over the tech news lately. A repeated weak point across the industry. I, for the most part, do not use GHA and you don't have to either. When I started my current job I set up Buildkite (replacing an unmaintained Concourse instance), wrote a ~100 line Python script using PyYAML and Jinja to give us a bit of composability, and then just wrote whatever CI scripting I needed. That's it, 100% written by me and my team other than those two libraries. And it works just fine. Took a week or two to get things going originally and we add new snippets every year or so. Don't Repeat Yourself and Not Invented Here are good principles but you can always opt out when you feel like there are reasons to. Time reinventing wheels can be an investment in the future. If you feel you _must_ always use public tools due to lack of resources, maybe rethink your timelines.

Replies (1)

  • @coderanger@cloudisland.nz I was recently looking at Buildkite, it’s interesting, but it can’t provide what Microsoft can. IMO with GitHub actions we get what we (don’t) pay for. In CPython for example, we now have many many jobs that run in the CI for each commit (both to branches and PRs, looking at the statistics, that’s a total of over 1.2 million minutes this month). It may not be ideal, but it is a pretty amazing amount of resources.

    Open ##2487226