© Jeff Dalton 2019
Jeff DaltonGreat Big Agilehttps://doi.org/10.1007/978-1-4842-4206-3_22

22. Continuous Integration

Jeff Dalton1 
(1)
Waterford, MI, USA
 

Description

Continuous Integration (CI) refers to the assembly of product components in incremental stages, using a purposeful strategy and defined procedures. CI integration is an approach to continuous testing and product integration that was first introduced in extreme programming (XP), but is now common in almost all successful agile projects. In a CI environment, an application is built and unit tested, and in some cases integration tested, using automated tools, each time new code is “checked-in” to the code management system.

../images/470826_1_En_22_Chapter/470826_1_En_22_Figa_HTML.jpg

Typical Roles

  • Configuration Manager (typically for larger teams)

  • Team Member

Desired Behaviors

  1. 1.

    Set up a code repository for configuration management.

     
  2. 2.

    Build servers and scripts to automate the integration and testing of checked-in code configured to build and compile the application at frequent intervals.

     
  3. 3.

    Commit code to the baseline repository as it is completed to enforce early integration testing.

     
  4. 4.

    Run automated unit and integration tests at frequent intervals.

     
  5. 5.

    Publish and review the results.

     
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.15.235.188