8 Martin Fowler, who first wrote about `Continuous Integration <http://martinfowler.com/articles/continuousIntegration.html>`_
9 (short: CI) together with Kent Beck, describes the CI as follows:
11 Continuous Integration is a software development practice where members of
12 a team integrate their work frequently, usually each person integrates at
13 least daily - leading to multiple integrations per day. Each integration is
14 verified by an automated build (including test) to detect integration errors
15 as quickly as possible. Many teams find that this approach leads to
16 significantly reduced integration problems and allows a team to develop
17 cohesive software more rapidly.
22 `Jenkins CI <http://jenkins-ci.org>`_ is an extensible continuous integration
29 `Buildbot <http://buildbot.net/buildbot/docs/current>`_ is a Python system to
30 automate the compile/test cycle to validate code changes.
36 .. todo:: Write about Mule
41 `tox <https://bitbucket.org/hpk42/tox>`_ is an automation tool providing
42 packaging, testing and deployment of Python software right from the console or
43 CI server. It is a generic virtualenv management and test command line tool
44 which provides the following features:
46 * Checking that packages install correctly with different Python versions and
48 * Running tests in each of the environments, configuring your test tool of
50 * Acting as a frontend to Continuous Integration servers, reducing boilerplate
51 and merging CI and shell-based testing.
57 .. todo:: Write about travis-ci