Computer Science

Seminar 10/14/09: An Introduction to Continuous Integration, James Edgeton

Continuous Integration is one of many software development techniques that are quickly being adopted by businesses today. Continuous Integration is a methodology of software design that attempts to provide functioning code at all times during the software development lifecycle, providing rapid feedback between developers and customers. There are three main components of Continuous Integration: a version control repository, a Continuous Integration server, and an automated build process. By implementing each of these strategies of Continuous Integration, a development team can reduce overall costs, and bugs in code are found more quickly.

Sources: Fowler, M. (2006, May 1). Continuous integration. Retrieved August 28, 2009, from http://martinfowler.com/articles/continuousIntegration.html

Knoernschild, K. (2008, December 11). Continuous integration: the project heartbeat. Retrieved from Burton Group website: http://www.burtongroup.com

Meera. (2008, December 15). The three pillars of continuous integration.  Retrieved September 2, 2009, from Architect Zone website: http://architects.dzone.com/print/6227

Subramaniam, V. (n.d.). Test driven development – part III: Continuous integration. Retrieved September 2, 2009, from Agile Developer website: http://www.agiledeveloper.com/articles/TDDPartIII.pdf

Varhol, P. (2008, July 15). Continuous integration: Was Fowler wrong? Retrieved September 2, 2009, from Server Side website: http://www.theserverside.com/news/thread.tss?thread_id=50060

Wells, D. (2009, September 3). Extreme programming: A gentle introduction. Retrieved September 12, 2009, from http://www.extremeprogramming.org/