From d5443ebb49f012870323044879119f95eb3d79c7 Mon Sep 17 00:00:00 2001 From: Seyi Ogunyemi Date: Thu, 20 Oct 2011 01:14:12 +0200 Subject: [PATCH] Fixed a typo in Martin Fowler's name and snuck in some stubs for Jenkins & Buildbot. --- docs/scenarios/ci.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/scenarios/ci.rst b/docs/scenarios/ci.rst index 013acd5..cd3d5dd 100644 --- a/docs/scenarios/ci.rst +++ b/docs/scenarios/ci.rst @@ -5,7 +5,7 @@ Continuous Integration Why? ---- -Martin Folwer, who first wrote about Continuous Integration (short: CI) together with Kent Beck, describes the CI as follows: +Martin Fowler, who first wrote about Continuous Integration (short: CI) together with Kent Beck, describes the CI as follows: Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage. @@ -14,13 +14,13 @@ Source: http://martinfowler.com/articles/continuousIntegration.html Jenkins ------- -Use it. +Jenkins CI (http://jenkins-ci.org) is an extensible continuous integration engine. Use it. Buildbot -------- - +Buildbot (http://buildbot.net/buildbot/docs/current) is a Python system to automate the compile/test cycle to validate code changes. Mule?