Information Technology Reference
In-Depth Information
Build Script
The build script is a single script, or set of scripts, you use to compile,
test, inspect, and deploy software. You can use a build script without
implementing a CI system. Ant, NAnt, make, MSBuild, and Rake are
examples of build tools that can automate the software build cycle, but
they don't provide CI by themselves. Some may use an IDE to build
software; however, since CI is a “hands-off” process, solely using
IDE-based builds won't cut it for CI. To be clear, using an IDE to run a
build is appropriate as long as you can run the same build without
using the IDE as well. Listing 1-4 shows an example of the shell of an
Ant script that runs through the type of processes typically performed
as part of a private build. 3
LISTING 1-4
Shell of an Ant Script to Perform a Build
<?xml version="1.0" encoding="iso-8859-1"?>
<project name="brewery" default="all" basedir=".">
<target name="clean" />
<target name="svn-update" />
<target name="all" depends="clean,svn-update"/>
<target name="compile-src" />
<target name="compile-tests" />
<target name="integrate-database" />
<target name="run-tests" />
<target name="run-inspections" />
<target name="package" />
<target name="deploy" />
</project>
Feedback Mechanism
One of the key purposes of CI is to produce feedback on an integration
build, because you want to know as soon as possible if there was a
problem with the latest build. By receiving this information promptly,
you can fix the problem quickly. Figure 1-3 shows an e-mail as a feed-
back mechanism. We demonstrate more feedback devices in Chapter 9.
Other feedback mechanisms include Short Message Service (SMS)
and Really Simple Syndication (RSS).
3. A more detailed example is provided at www.integratebutton.com.
Search WWH ::




Custom Search