Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage.
J. Wrenn, and S. Krishnamurthi. Proceedings of the 2019 ACM Conference on International Computing Education Research, page 131--139. New York, NY, USA, ACM, (2019)
V. Lappalainen, J. Itkonen, V. Isomöttönen, and S. Kollanus. ITiCSE '10: Proceedings of the fifteenth annual conference on Innovation and technology in computer science education, page 63--67. New York, NY, USA, ACM, (2010)
V. Lappalainen, J. Itkonen, V. Isomöttönen, and S. Kollanus. ITiCSE '10: Proceedings of the fifteenth annual conference on Innovation and technology in computer science education, page 63--67. New York, NY, USA, ACM, (2010)
P. Abrahamsson, A. Hanhineva, and J. Jäälinoja. Business Agility and Information Technology Diffusion, volume 180 of IFIP International Federation for Information Processing, Springer Boston, 10.1007/0-387-25590-7_14.(2005)
S. Kollanus, and V. Isomöttönen. ITiCSE '08: Proceedings of the 13th annual conference on Innovation and technology in computer science education, page 124--127. New York, NY, USA, ACM, (2008)
K. Keefe, J. Sheard, and M. Dick. ACE '06: Proceedings of the 8th Austalian conference on Computing education, page 91--100. Darlinghurst, Australia, Australia, Australian Computer Society, Inc., (2006)
A. Ayerbe, and I. Vazquez. Computer Software and Applications Conference, 1998. COMPSAC '98. Proceedings. The Twenty-Second Annual International, (August 1998)