2 ms·
You're making a lot of assumptions about how such a move would be done which I don't feel are warranted. You're picking the hardest most painful option and then
by marcinzm 8y ago
You're making a lot of assumptions about how such a move would be done which I don't feel are warranted. You're picking the hardest most painful option and then using it to claim the process is painful rather than that the option you chose is painful.
If I was moving many small repos into a single mono repo then I'd do it one repo at a time. Presumably your small repos are independent entities so there's no reason to do a single massive switch. Transition each repo to the new build system inside the existing repo. Once that works then you can transition that repo into the mono-repo and tie together the build systems. No need to stop releases, no massive chance of everything failing, no weeks of debugging while the world is stopped, etc. Rinse and repeat until everything is moved over. Process becomes more optimized and less error prone with each repo that is moved over.
- bluGill 8y agoNow I lose lots of weekends making each separate move.
- marcinzm 8y agoWhy weekends? Small moves means you do it during the week and during regular working hours. Done in branches with CI support so that it's pretty unlikely to break anything. If doing regular releases require you to be spending your weekends then you have bigger issues to fix first. Spread it over however long it takes. Why are you trying to make your life more difficult?
- bluGill 8y agoI have done this. Regardless of when you do the move everybody who works in the repo being moved is down for several hours at best if you do it during working hours.