2 ms·
Same situation here. And we have always had tests, too. Hard to force mixed fleet behavior in most tooling, though. And teams grow, such that relying on code
by taeric 5y ago
Same situation here. And we have always had tests, too. Hard to force mixed fleet behavior in most tooling, though. And teams grow, such that relying on code review to catch things is really a best intentions.
Putting it in your face that you are changing two projects is about the best I can offer here. I would cede that this, too, is mainly a best intentions. But having as close to 1:1 between code changes, deployment changes, and code reviews at least puts things on mainly equal footing.
That is, when the explanation of why some code can't deploy together is that they are in two projects, and you can see that by them being separate repositories, that feels easier than knowing that two parts of a single repository have to deploy separately.
- klodolph 5y agoIt just seems like such a miniscule benefit, and you have to deal with the massive headache of a multi-repo setup. If you don't want people making changes to multiple projects at the same time, it would be trivial to add a pre-submit check to enforce that anyway. There's no need to switch your entire repository layout just to remind people that the code in different folders belongs to different projects.
- taeric 5y agoI will fully cede questionable ROI on this whole exercise. But, I will argue that cuts both directions. That is, I would not push to move from one form to the other. I do like multiple projects being as independent as I can make them, though.