3 ms·
All of these are solved with tooling. - dont have multiple monorepos - use blaze or similar and run all downstream tests, the binary for your ml model include
by joshuamorton 2y ago
All of these are solved with tooling.
- dont have multiple monorepos
- use blaze or similar and run all downstream tests, the binary for your ml model includes pytorch whether you build from source or requirements.txt.
- other people committing doesn't matter if you are isolating presubmits and similar.
- using a blaze-like you never compile the whole monorepo
- code owners etc. makes this straightforward.
Like, as someone whose career has been mostly at Google, these are not problems I encounter at all, or only in cases where you'd have similar scope of problems no matter the repo structure.
- hughesjj 2y ago> other people committing doesn't matter if you are isolating presubmits and similar. Could you elaborate on this one?
- joshuamorton 2y agoIf you only need to run the tests you affect, and only need to sync and update files touched in your CL, external changes are generally not impactful, sync & submit is a quick process even if people are submitting things elsewhere. It's only a problem if someone submits a file you're touching, in which case you just have standard merge conflict issues.