Re:Experiment: The costs of slow build times
by ohgodplsno on Friday December 09, 2022 @07:03AM
(#33920365)
Caching is pretty damn simple with any sensible build tool that simply stores hashes of files and modules. Caching in the JVM ecosystem is pretty much free, for example.
[ Parent
| on HN ]
Re:Experiment: The costs of slow build times
by carreau on Friday December 09, 2022 @07:16AM
(#33920434)
Sure, but you seem to be read this blog post in the narrow view of building as only "compiling an artifact" and not running the test suite across many platforms/condition, or any other work. I mean the author even points out that building the kernel is only a use-case that takes time for measurement purposes. For some projects I work on the compilation itself takes maybe 1/10 max of the total build and test. So even with infinite agressive compilation caching I would not gain much.
Re:Experiment: The costs of slow build times
by ohgodplsno on Friday December 09, 2022 @08:33AM
(#33921028)
Nope, our Android app has caching, both for building APKs/AABs, but also for test suites. PRs run the entire test suite (on too many variants, even, I forgot to remove some unneeded stuff), what hasn't changed or hasn't been impacted by said changes simply gets a FROM-CACHE and isn't reran.
Re:Experiment: The costs of slow build times
by ninkendo on Friday December 09, 2022 @09:39AM
(#33921632)
That's great for your android app, and you're lucky you have such a thing. But your experience is not generally applicable to all of software development. There are many, many, many build systems out there in the wild that do not support the ability to know what unit tests are affected by what code changes. I'd wager something like 99% of them.
Re:Experiment: The costs of slow build times
by substation13 on Friday December 09, 2022 @08:01AM
(#33920748)
You can cache tests too if you properly capture the inputs