moinsen / Software historyDE ↗
← 2000

Event

Software mehrmals täglich zusammenführen und prüfen

Context and research status
  • Kennung: 2000-kontinuierliche-integration
  • Zeitpunkt: 10. September 2000
  • Datumsgenauigkeit: Tag / day
  • Art: Erfahrungsbericht und Entwicklungspraxis / experience report and development practice
  • Kategorien: Sprachen und Techniken, Prägende Akteure, Markt und Alltag
  • Beteiligte: Martin Fowler und Matthew Foemmel: Autoren; Projektteam bei Thoughtworks: Praxisbeispiel
  • Region: international / international

When several people work on a program, their changes can cause problems when combined. In 2000 Martin Fowler and Matthew Foemmel described a project where software was automatically built and tested several times a day. The aim was to expose integration errors early and make them easier to fix. They identified continuous integration as a practice of Extreme Programming. Source

For their example, the authors reported around 50 team members, 200,000 lines of code and several dozen builds a day. Their successful build included around 150 test classes. These figures describe that project; the authors said they knew of no scientific study of their productivity assessment. Project figures and limits

In 1978 Stuart Feldman had already described the Make build tool, which managed dependencies and required build commands. Automated build steps alone, however, are not continuous integration. Source

The article describes a specific way of working; it does not establish that automated builds were invented in 2000 or give a general error rate. The Agile Manifesto was formulated the following year. Source

Sources

Offen

Weitere frühe Praxiserfahrungen und die Geschichte automatisierter Build-Werkzeuge untersuchen. / Investigate further early experiences and the history of automated build tools.