知识卡片
项目仓库按交付分组
构建项目是产出一个离散组件的代码集合,代码库可含多个项目,仓库则是版本控制的边界。共同构建、经常一起修改的项目适合同仓;独立交付、需要强边界或权限隔离的项目适合分仓。单仓便利跨项目版本一致,但容易形成文件级偷依赖;多仓隔离更强,却增加跨仓变更协调。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 用流水线实现基础设施交付 · 查看原书依据
Consider the following design forces: Separating projects into their own repositories makes it easier to maintain boundaries at the code level. Having too many people working on code in a single repository can create friction and conflicts. Most source control systems manage permissions at the
参考来源
- 位置:《Infrastructure As Code》第16章《用流水线实现基础设施交付》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch16.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“构建项目是产出一个离散组件的代码集合,代码库可含多个项目,仓库则是版本控制的边界”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:Consider the following design forces: Separating projects into their own repositories makes it easier to maintain boundaries at the code level. Having too many people working on code in a single repository can create friction and conflicts. Most source control systems manage permissions at the