3 ms·
Monorepos are a problem born of CI which can't cope with cross project dependencies properly. People have solved the problem by pumping everything together, but
by weebull 3y ago
Monorepos are a problem born of CI which can't cope with cross project dependencies properly. People have solved the problem by pumping everything together, but it's the wrong answer.
Fix CI and the problem goes away.
- vlovich123 3y agoSorry no. CI and monorepos are at best tangentially related. Dependency tracking across repos is a PITA which inhibits code reuse - git sub modules suck as do whatever that alternative git submodule concept is called (subtree?). Code repos like Cargo and NPM can help but even still it’s an annoying dance to update dependencies in multiple downstream projects. And if there’s a code change you need to make, it’s a 3-way orchestration of new api, update downstream dependencies, remove old api.
- weebull 3y agoThat's exactly my point. Cross dependencies is exactly the problem I want CI to solve.
- vlovich123 3y agoLike the CI system automatically push code commits updating downstream dependencies that reference the upstream repo? Or something else?