Information Technology Reference
In-Depth Information
The steps in a CI scenario will typically go something like this.
1. First, a developer commits code to the version control reposi-
tory. Meanwhile, the CI server on the integration build machine
is polling this repository for changes (e.g., every few minutes).
2. Soon after a commit occurs, the CI server detects that changes
have occurred in the version control repository, so the CI server
retrieves the latest copy of the code from the repository and then
executes a build script, which integrates the software.
3. The CI server generates feedback by e-mailing build results to
specified project members.
4. The CI server continues to poll for changes in the version con-
trol repository.
Figure 1-1 illustrates these parts of the CI system.
The following sections describe the tools and players identified in
Figure 1-1 in more detail.
Feedback
Mechanism
Developer
Generate
Commit Changes
:
Commit Changes
Poll
Build Script
Developer
Compile Source Code,
Integrate Database,
Run Tests,
Run Inspections,
Deploy Software
Subversion
Version Control
Repository
CI Server
Integration Build
Machine
Commit Changes
Developer
The components of a CI system
FIGURE 1-1
Search WWH ::




Custom Search