You can see why go is how it is due to monorepos. I think at least I can see how his willl be a train wreck with ruby :)
-
-
-
You have to separate external and internal deps. External deps you have to soak the coordination cost yourself, because you can’t change that reality. Ruby monorepos work fine, but you gotta gem update a lot :)
- Još 6 drugih odgovora
Novi razgovor -
-
-
I prefer polyrepo as I want one artifact per repo, whether the artifact is deployed, or simply pushed to an artifact repository. Also like seperate version scheme per artifact. Upticking the version when their are no changes can get confusing.
-
You can have all those things in a monorepo, if you like.
- Još 9 drugih odgovora
Novi razgovor -
-
-
I really really dislike having to write filters for every git based CI trigger with a mono repo. "Run this job if these change, the job if these change, not those, always these". The poly repo makes that far more natural, and then you can use
@ZuulCI to tie them back together. -
I agree, that’s a downside. I think it’s worth it for the upside.
- Još 3 druga odgovora
Novi razgovor -
-
-
Tweet je nedostupan.
-
Yes. At scale code management is hard, full stop. I just prefer the trade off I get organizationally.
Kraj razgovora
-
-
-
Yes. You nailed that last paragraph.
-
Thanks!
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.