A Hundred Days of Continuous Integration
A Hundred Days of Continuous Integration
复制标题
一百天的持续集成
DOI：
--
复制
发表时间：
2008
期刊：
影响因子：
--
通讯作者：
A. Miller
中科院分区：
文献类型：
--
作者：
A. Miller
许多敏捷团队使用持续集成（CI）。它是一种极端的编程实践，已被社区广泛采用[1]。它到底有多有效？与尝试永远不中断构建的更快速的签入过程相比，维护CI服务器和修复构建中断的工作是否节省了时间？虽然有很多轶事证据存在的好处CI有很少的数据来支持这一点。你如何说服团队和管理层，itpsilas值得采用，以及如何最好地做到这一点？本报告概述了我们在分布式团队环境中使用CI的经验，并试图回答这些问题。
Many agile teams use continuous integration (CI). It is one of the extreme programming practices and has been broadly adopted by the community [1]. Just how effective is it? Does the effort of maintaining the CI server and fixing build breaks save time compared to a lengthier check-in process that attempts to never break the build? While much anecdotal evidence exists as to the benefits of CI there is very little in the way of data to support this. How do you convince teams and management that itpsilas worth adopting and how best to do it? This report outlines our experience with CI in a distributed team environment and attempts to answer these questions.