4 ms·
In the past, Burt says, when a build took 4 hours instead of 45 minutes... Wow! And they've apparently spent a tremendous amount of time and resources optimizi
by jobu 14y ago
In the past, Burt says, when a build took 4 hours instead of 45 minutes...
Wow! And they've apparently spent a tremendous amount of time and resources optimizing the build process.
It's been 10 years since I worked on a project where a build took more than a few minutes. Back then, a project I worked on took over 3 hours to compile on a 4-processor Solaris box. The PC technology improved so drastically that in a few years we were able to get it cross-compiling to Solaris from a Linux box in under 20 minutes.
- larsberg 14y agoNot terribly surprising. Back when I worked at MSFT, I spent ~3 months (and had two other developers and a couple of build engineers working with me) taking our 3 _day_ build and getting it down to ~12 hours. But, that was several times larger than this system (even then), and it was about 7 years ago. And it had to support all sorts of weird things such as "which compiler do you use to build the compiler; the compiler you just built, the compiler you last used, or the compiler we last shipped?" for a very large configuration of compilers, runtime platforms, etc.
- bcbrown 14y agoWhen I worked there a couple years ago, requesting a custom Windows build still took overnight, if you wanted more exhaustive testing than just xcopying a couple binaries.