Re:We Halved Go Monorepo CI Build Time
by treis on Sunday June 26, 2022 @04:06PM
(#31887446)
I don't think it's recreating a monorepo. What you're looking for is something like a DB transaction where all the merges in different repos succeed or everything gets rolled back.
[ Parent
| on HN ]
Re:We Halved Go Monorepo CI Build Time
by mattnewton on Sunday June 26, 2022 @04:15PM
(#31887529)
Maybe I am missing something: to do that you need some kind of “meta-repository” linking commits between all the different sub repos in some order, no? If that happens for a significant portion of the commits in a repo, isn’t that basically equivalent to a mono repo with git submodules or something?
Well a meta repo isn't a mono repo. In that situation you can still update individual repos. Analogous to running a DB operatioj without a transaction.
But that said, no I don't think you need a meta repo. You need something. Call it a Change set. MVP would be say merge commits in 4 repos. If any fail then revert. If they all succeed then deploy in a specified order.