Thread

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

317 points · 408 comments · julian_digital

azkalam · 1790019824 · focus · HN ↗
If you can pay the setup cost, Bazel will get you build times ~10s with a warm cache for even massive projects.
1. criemen · 1790022309 · focus · HN ↗
  I lead a bazel conversion for a pretty complex piece of software written in 5+ programming languages and shipping native binaries to all 3 major OSes a few years ago, and it took multiple years to get it done.
  For a less complex project (1 programming language, still shipping to all 3 major OSes), with my knowledge and agents I got the bazel conversion done in 2 weeks.
  The setup cost for bazel just went down by a lot, and I don't think the industry as a whole is aware of that yet.
  1. rokob · 1790022674 · focus · HN ↗
    Were any of those using JS/TS? I've seen Bazel perform wonders with many compiled languages, but I'm not impressed with the JS ecosystem.
    criemen · 1790024107 · focus · HN ↗
    Nothing substantial, no. I've never personally experienced builds to be so slow to begin investigating bazel as an option for JS/TS.
    Tsgo, oxlint, caching dependencies etc. what linear outlined in their blog post would be more impactful for the average TS project I've worked on.

Unofficial Hacker News client; not affiliated with Y Combinator.