Learn how Rational® Build Forge can extend
a simple compile and package build process by adding customization and deployment
capability. Go from a manual method to automating: checking for code changes;
getting the latest source; compiling and packaging; customizing; copying to and
restarting a deployment server; and sending e-mail notification that a new version
is available. This series shows you how to implement a build management system
that uses and extends your existing automation technologies. With this 2-part series, go from zero to 96 bpd (builds per day) in two days.
Objectives
Build Tomcat from scratch
Automate the build using Build Forge
Extend build management to deploy Tomcat
Add an automated custom tweak to the deployment parameters
Get 'live' versions of Tomcat code from the repository.
Configure Build Forge to periodically check for updates to the code, and
trigger builds accordingly.
Prerequisites
It is assumed that you have completed Part 1 in
this series. It is also assumed that you have some understanding of building
applications based on Java™ technology. Build Forge is language agnostic, but the
Tomcat project is written in the Java language. Experience with Apache Ant and Subversion is
helpful, but not required.
