Continuous Integration (CI) System

From GM-RKB
Jump to navigation Jump to search

A Continuous Integration (CI) System is an software integration system that can fascilitate continuous integration task (can perform frequent code builds and code tests).



References

2022

2009


  • (Kofman, 2009) ⇒ Vlad Kofman. (2009). “The Best Continuous Integration Tools." February 18, 2009
    • QUOTE: The term “continuous integration” refers to a process that builds and tests code on a frequent basis. It was coined by Martin Fowler and Kent Beck, who first wrote about this process near the turn of the millennium.

      The continuous integration servers constantly monitor source code repositories and as soon as new changes/commits are detected, they initiate a new build cycle. The build cycle actually involves code compilation and, in addition, may involve various tests and code analysis. If the process encounters errors, it may notify the build master or the culprit who checked in broken/invalid code.

      The process can be summarized in these four steps:

      • Team members check in code artifacts into the source control repository.
      • The automated build server constantly monitors the repository.
      • New code is continuously checked out [by this server].
      • A new project build is continuously integrated and any issues are reported in real time.