Software Integration Task

From GM-RKB
Jump to navigation Jump to search

A Software Integration Task is a software engineering task that merges software system changes (e.g. developer working copies) into a mainline repository.



References

2022

  • (Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/Continuous_integration#Rationale Retrieved:2022-10-4.
    • When embarking on a change, a developer takes a copy of the current code base on which to work. As other developers submit changed code to the source code repository, this copy gradually ceases to reflect the repository code. Not only can the existing code base change, but new code can be added as well as new libraries, and other resources that create dependencies, and potential conflicts.

      The longer development continues on a branch without merging back to the mainline, the greater the risk of multiple integration conflicts and failures when the developer branch is eventually merged back. When developers submit code to the repository they must first update their code to reflect the changes in the repository since they took their copy. The more changes the repository contains, the more work developers must do before submitting their own changes. Eventually, the repository may become so different from the developers' baselines that they enter what is sometimes referred to as "merge hell", or "integration hell", where the time it takes to integrate exceeds the time it took to make their original changes.

2016

  1. For computer systems, the term "systems integration" has included the plural word "systems" although the singular form has also been used in referring to computer systems.