Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 7a4a89d

Browse filesBrowse files
author
Johannes Seitz
committed
Added paragraph "Why CI?"
1 parent 0cb273d commit 7a4a89d
Copy full SHA for 7a4a89d

File tree

Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed

‎docs/scenarios/ci.rst

Copy file name to clipboardExpand all lines: docs/scenarios/ci.rst
+5Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,11 @@ Continuous Integration
55
Why?
66
----
77

8+
Martin Folwer, who first wrote about Continuous Integration (short: CI) together with Kent Beck, describes the CI as follows:
9+
10+
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.
11+
12+
Source: http://martinfowler.com/articles/continuousIntegration.html
813

914
Jenkins
1015
-------

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.