4 ms·
why does your CI do all that after you start the build if it happens every time? Developer time is expensive. Scale up ahead of time, so there’s always a machi
by danielheath 4y ago
why does your CI do all that after you start the build if it happens every time? Developer time is expensive.
Scale up ahead of time, so there’s always a machine ready. Prefetch the repository / packages when CI workers start, so they’re already installed before a build is triggered. Use your imagination - CI doesn’t have to suck.
- mgaunard 4y agoIf you scale up ahead of time then it's not really on-demand, that means you have dedicated hardware you're paying much more for.
- danielheath 4y agoThe marginal cost to keep a large-ish spot instance running 99% of the time is dirt cheap (eg $400/mo to keep one extra c7g.8xlarge running). If you're paying for an engineering team, that's a rounding error.