Continuous integration

See also Continuous Delivery

Snippet from Wikipedia: Continuous integration

In software engineering, continuous integration (CI) is the practice of merging all developers' working copies to a shared mainline several times a day. Grady Booch first proposed the term CI in his 1991 method, although he did not advocate integrating several times a day. Extreme programming (XP) adopted the concept of CI and did advocate integrating more than once per day – perhaps as many as tens of times per day.

GitHub Topics

Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production. A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.

## ToDo ##

  • CircleCI
  • Codeship
  • Concourse CI
  • Continua CI
  • GitLab CI
  • Gump
  • Hudson
  • Hydra
  • Jenkins X
  • Nevercode
  • ProductionMap
  • Semaphore
  • Shippable
  • Snap CI
  • Solano CI
  • TeamCity
  • ci/ci.txt
  • Last modified: 2022/08/17 12:34
  • by Henrik Yllemo