‹ BackHN Continuity

Thread

AI coding has made CI a bottleneck, so we reworked ours to keep up

317 points · 408 comments · julian_digital

  1. cyberax · · focus · HN ↗
    Heh. I fixed my CI&#x2F;CD flows last year to be no more than 60 seconds: <a href="https:&#x2F;&#x2F;pics.ealex.net&#x2F;share&#x2F;2IpZSt2cxrKWzeUokNNmk4eRI1jjzF2bDhtAS1nD5cKSvlKFWrhbdpQlPvzHSuzXNJk" rel="nofollow">https:&#x2F;&#x2F;pics.ealex.net&#x2F;share&#x2F;2IpZSt2cxrKWzeUokNNmk4eRI1jjzF2...

    And this includes _full_ linting and unit tests.

    I did that by self-hosting Github Runners, using Podman to build images (it doesn&#x27;t squirt your build context through a socket every time!), and using Docker images as content-addressable cache.

    I will do a write-up about it this week...

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.