持续交付-发布可靠软件的系统方法-(英文版)

目录part i: foundations / 基础篇 1chapter 1: the problem of delivering software / 软件交付的问题 3introduction / 引言 3some common release antipatterns / 一些常见的发布反模式 4antipattern: deploying software manually / 反模式：手工部署软件 5antipattern:deploying to a production-like environment only after development is complete / 反模式：开发完成之后才向类生产环境部署 7antipattern: manual configuration management of production environments / 反模式：生产环境的手工配置管理 9can we do better? / 我们能做得更好吗 10how do we achieve our goal? / 如何实现目标 11every change should trigger the feedback process / 每次修改都应该触发反馈流程 13the feedback must be received as soon as possible / 　必须尽快接收反馈/ 14the delivery team must receive feedback and then act on it / 交付团队必须接收反馈并作出反应 15does this process scale? / 这个流程可以推广吗 16what are the benefits? / 收效 17empowering teams / 授权团队 17reducing errors / 减少错误 18lowering stress / 缓解压力 20deployment flexibility / 部署的灵活性 21practice makes perfect / 多加练习，使其完美 22the release candidate / 候选发布版本 22every check-in leads to a potential release 23principles of software delivery / 软件交付的原则 24create a repeatable,reliable process for releasing software / 为软件的发布创建一个可重复且可靠的过程 24automate almost everything / 将几乎所有事情自动化 25keep everything in version control / 把所有的东西都纳入版本控制 26if it hurts, do it more frequently, and bring the pain forward / 提前并频繁地做让你感到痛苦的事 26build quality in / 内建质量 27done means released / “done”意味着“已发布” 27everybody is responsible for the delivery process / 交付过程是每个成员的责任 28continuous improvement / 持续改进 28summary / 小结 29chapter 2: configuration management / 配置管理 31introduction / 引言 31using version control / 使用版本控制 32keep absolutely everything in version control / 对所有内容进行版本控制 33check in regularly to trunk / 频繁提交代码到主干 35use meaningful commit messages / 使用意义明显的提交注释 37managing dependencies / 依赖管理 38managing external libraries / 外部库文件管理 38managing components / 组件管理 39managing software configuration / 软件配置管理 39configuration and flexibility / 配置与灵活性 40types of configuration / 配置的分类 41managing application configuration / 应用程序的配置管理 43managing configuration across applications / 跨应用的配置管理 47principles of managing application configuration / 管理配置信息的原则 47managing your environments / 环境管理 49tools to manage environments / 环境管理的工具 53managing the change process / 变更过程管理 53summary / 小结 54chapter 3: continuous integration / 持续集成 55introduction / 引言 55implementing continuous integration / 实现持续集成 56what you need before you start / 准备工作 56a basic continuous integration system / 一个基本的持续集成系统 57prerequisites for continuous integration / 持续集成的前提条件 59check in regularly / 频繁提交 59create a comprehensive automated test suite / 创建全面的自动化测试套件 60keep the build and test process short / 保持较短的构建和测试过程 60managing your development workspace / 管理开发工作区 62using continuous integration software / 使用持续集成软件 63basic operation / 基本操作 63bells and whistles / 铃声和口哨 63essential practices / 必不可少的实践 66don’t check in on a broken build / 构建失败之后不要提交新代码 66always run all commit tests locally before committing, or get your ci server to do it for you / 提交前在本地运行所有的提交测试，或者让持续集成服务器完成此事 66wait for commit tests to pass before moving on / 等提交测试通过后再继续工作 67never go home on a broken build / 回家之前，构建必须处于成功状态 68always be prepared to revert to the previous revision / 时刻准备着回滚到前一个版本 69time-box fixing before reverting / 在回滚之前要规定一个修复时间 70don’t comment out failing tests / 不要将失败的测试注释掉 70take responsibility for all breakages that result from your changes /为自己导致的问题负责 70test-driven development / 测试驱动的开发 71suggested practices / 推荐的实践 71extreme programming (xp) development practices / 极限编程开发实践 71failing a build for architectural breaches / 若违背架构原则，就让构建失败 72failing the build for slow tests / 若测试运行变慢，就让构建失败 73failing the build for warnings and code style breaches / 若有编译警告或代码风格问题，就让测试失败 73distributed teams / 分布式团队 75the impact on process / 对流程的影响 75centralized continuous integration / 集中式持续集成 76technical issues /技