I’m not sure how to define this, what I can say is that right now it doesn’t seem to be an issue, and if it would take double the time I think it would still be OK, at least when building the whole project for a PR. If it takes longer it should force us to be more careful before making a PR.
What I think would be more interesting , or a different way of phrasing the question:
- How to avoid building everything? (when most of the code is unchanged)
- How to shift part of the load to the developer/contributor?
I’m not sure how to do the second point, but it could for example build for a subset of CPU’s and a subset of the touched applications. It wouldn’t catch everything but it would help reduce the amount of unnecessary builds. A good starting point would be to force/incite us to run the static checks.