知识卡片
共享测试环境拖慢反馈
多个团队共用不稳定数据库和测试环境时,互相干扰会让团队把改动长期留在分支,直到接近上线才集成。改善反馈速度要隔离关键测试数据与依赖,并恢复持续集成,而非把环境冲突当作代码故障。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第3章《Anti-Patterns: Distributed Monoliths》(源文件:`_epub-src/OPS/ch03.xhtml`,归一化正文 [46189:50434))
- 结论依据:原文说分布式单体的不稳定共享环境会导致分支膨胀和集成延后,使反馈周期变慢。
- 原始内容:No continuous integration : Software should be integrated all the time. Due to the instability that bad environments create with distributed monoliths, people will do all they can to be isolated and stable and commit code early and often. This results in branch explosion, and teams holding back everything in feature branches. And you only get feedback getting close to prod. This is bad because it delays feedback cycles, and makes the whole engineering process expensive and inefficient.