Monorepo

In the company I am working, we are using a multirepo approach to organize our source code. Unfortunately, with a growing number of repos we ran into problems. It became difficult to search for code, because you need all project checkout out and up to date Our conservative way of sharing code lead to a lot of overhead to keep the other ends up to date Therefore the inhibition threshold to change something increased because you wnt to avoid the overhead of creating all those branches with the new version reference You never know (immediately) if an update of a dependency broke something on the integrating side, because you don’t run their test suite....

October 30, 2017 · 3 min · Markus Ruepp