Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Branching Assessment  Branching Assessment   Continuous integration Build Status   Continuous integration Build Status

Lifecycle   »   Development   »   Continuous integration

Continuous Integration is a technique used during the development of software solutions. It involves the submitting or committing of source code to a central code repository. This process oftentimes also includes the automated running of tests and, on successful completion of these tests, the copying of successful code to a release-ready platform.

Continuous Integration allows the team to deliver the latest stable tested and verified versions of software to desired platforms in an automated manner. This can be tailored to particular environments and selected versions of libraries, release criteria or database platform.

In general, the development team employ Continuous Integration software that can be configured and automated to be deployed using a number of different methods such as via a GUI interface, via a command line or API control.

Continuous Integration implies that re-builds are carried out with every change that is made by the development team and not just for the purposes of nightly builds. the objective of Continuous Integration is that you demand and get early warnings that someone or something has broken the build.

Project team developers submit their code frequently throughout the day, so they generate many integrations of the combined source during the development day. This is an important technique to repeatedly validate the quality and integrity of the added code but also to ensure the whole code base is integrated and working collaboratively to the same target infrastructure, environment settings and database schema etc.

The added integration is validated by an automatic build script to identify and report integration inconsistencies and errors back to a developer. The build script will often report status openly to the team. We deal with this in the section on Extreme Feedback Devices.


 Branching Assessment     Branching Assessment   Continuous integration Build Status    Continuous integration Build Status

Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z

#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
Continuous integration


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 316  Page: 268/444  Progress: 60.4%
 About    |    Author 
Follow @BigAgileToolkit

This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL ( and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.