Balancing quality assurance and safety against speed and convenience

Many use CI servers to produce automated builds. Typically, you'll run tests before packaging and deploying the application.

There is a tradeoff though between level of testing and the speed of the build. Supposing you've followed good testing practices, you have unit, e2e, and integration tests. Running all of these on every build can take quite some time, and cause builds to queue, when to do the fancy time-costly tests requires pulling containers, starting a full stack, and running through an extensive suite.

Not running the full test suite on every build (including feature branches) can result in breakages that take time to surface. The team gets 8 tickets down the road, and in prep for a release discovers some nasty issue which sets it back, and then has to trace back to where that problem was introduced, when it could have been caught on the feature branch.

How does HN balance these things? Some companies I've talked to hate the idea of anything longer than a 5 minute build; others have very lengthy builds that produce extremely high levels of quality assurance.

How do you balance these two competing concerns?