logoalt Hacker News

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

34 pointsby julian_digitaltoday at 7:23 PM19 commentsview on HN

Comments

classictraffictoday at 8:32 PM

> Moving our workloads off GitHub Actions to third-party runners with faster CPUs, higher-performance storage, and better cache infrastructure gave us faster machines to run the same pipeline on

Yeah, was not surprised to read this. Actions is convenient if you already use GitHub, but it can also be pretty slow. Given reliability is also a major issue with GitHub these days I expect to see more orgs moving to different pipelines

aliclarktoday at 8:28 PM

In my case it's not the CI that's the bottleneck. It's the human testing side. Does it work, sure. But does it actually do the thing we want (and more importantly) does it do it in a way our customers will understand and actually like?

algestentoday at 8:28 PM

Good thing Linear has been finished for a long time doesn't need more features, so AI coding can go slow. Oh damn, it's busy becoming the next Jira :(

azkalamtoday at 7:43 PM

If you can pay the setup cost, Bazel will get you build times ~10s with a warm cache for even massive projects.

show 1 reply
mraza007today at 7:57 PM

Agentic Coding has been a huge strain on CI, I have been using Bazel to improve our build times and ultimately building customized runners to improve our CI

Anyways great blog post from linear team a lot to learn from it

inshardtoday at 8:27 PM

I just feel apps like linear are increasingly getting in the way of full send agentic development where sub agent orchestration is done through agent to agent messaging, work trees, on demand git restructuring and epoch specific coordination plains, often .md files. The smaller the human component of total product development gets, the more this may be the case.

d_sctoday at 7:50 PM

vitest load balancing on test duration times instead of by file would be a nice performance win

show 1 reply
alexnewmantoday at 7:59 PM

My recent winnowwallet.com still has build times of over 10 minutes. I'm convinced the agent really wants build times around 5m to move at a quick pace. Also to not drive me insane. It took a ton of work to get it down from 45 minutes because my tests launch a full version of the app, and walk it through major usecases while recording video and screenshots. I then use AI to qa this. It also generates its webpage this way. All from CI/CD

hrpnktoday at 8:21 PM

[dead]

xracytoday at 8:05 PM

Maybe I'm alone in this, but as someone who is in tech, I don't know what CI is, and I don't think it's unreasonable to expect it to have an expansion within the article the first time you use it...

AI is in the cultural zeitgeist, but you gotta expand most other things at least once.

show 5 replies